Caching read-only data in a weblogic cluster: Need Help
Hello,
I'm working on the development of a web site that will be based on a weblogic cluster spread across several weblogic instances running on several unix boxes.
To avoid frequent hits to the database, I would like hold a huge amount of data in the application's in-memory cache. The idea is to query the database at startup and store the results in memory for the life of the JVM.
I have three questions around this:
1. Is it advisable to store this data in the form of read-only entity beans?
2. If not, what other options do I have?
3. In some rare cases, a back-end script might change (and commit) data contained in one or two of these 64000 records. What is the best way of propagating these data changes across the cluster?
Any help in this regard would be greatly appreciated.
Regards,
Dipak Jha
