Using Read-Only Entity Beans
As we've seen throughout this chapter, entity beans provide an object view of persistent and transactional data. However, not all persistent data is truly transactional. Many Web applications are dominated by reads and can even tolerate slightly stale data. The WebLogic Server offers an option called read-only entity beans to provide greater performance for read-intensive applications.
The advantage of read-only entity beans is that their data can be cached in memory, in many servers in the cluster. Read-only entity beans do not use expensive logic to keep the distributed caches coherent. Instead, the deployer specifies a timeout value, and the entity bean's cached state is refreshed after the timeout has expired. ...
Get J2EE™ Applications and BEA™ WebLogic Server™ now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
