|Cache coordination per entity type [message #1066844]
||Thu, 04 July 2013 13:34
| Christoph Smaul
Registered: April 2012
i am using EL in a clustered JBoss environment and my data can be devided into
a) "mass data" that is updated and inserted quite often, but also read often enough to make caching pay off. This data has dependencies to the data of type b), but can be devided horizontally into independent sections (per user).
b) "base data" which is not updated often but read frequently
For type b) data, cache coordination is optimal, since it is not updated that often so invalidation messages will not be the problem.
For type a), I plan to stick users to a single node to be able to benefit from caching. The problem is, I cannot afford to have invalidation messages for this kind of data and I do not want to disable caching on the nodes either.
Is there any way to disable cache coordination for certain entity types while still keeping the local L2 cache for these?
Powered by FUDForum
. Page generated in 0.01782 seconds