Best Practice for caching global list of objects
328927Jul 16 2003 — edited Aug 28 2003Here's my situation, (I'm guessing this is mostly a question about cache synchronization):
I have a database with several tables that contain between 10-50 rows of information. The values in these tables CAN be added/edited/deleted, but this happens VERY RARELY. I have to retrieve a list of these objects VERY FREQUENTLY (sometimes all, sometimes with a simple filter) throughout the application.
What I would like to do is to load these up at startup time and then only query the cache from then on out, managing the cache manually when necessary.
My questions are:
What's the best way to guarantee that I can load a list of objects into the cache and always have them there?
In the above scenario, would I only need to synchronize the cache on add and delete? Would edits be handled automatically?
Is it better to ditch this approach and to just cache them myself (this doesn't sound great for deploying in a cluster)?
Ideas?