Caching strategies
Read-only
This strategy is useful for data that is read frequently but never updated. This is by far the simplest and best-performing cache strategy.
Read / write
Read/write caches may be appropriate if your data needs to be updated.
They carry more overhead than read-only caches.
In non-JTA environments, each transaction should be completed when Session.close() or Session.disconnect() is called.
Nonstrict read / write
This strategy does not guarantee that two transactions won't simultaneously modify the same data.
Therefore, it may be most appropriate for data that is read often but only occasionally modified.
Transactional
This is a fully transactional cache that may be used only in a JTA environment.
No comments:
Post a Comment
Note: only a member of this blog may post a comment.