Felix, No, not terribly high volume. However, the non-admin pages are high volume. The reason that I want cache visibility (preferably using the transparent entity bean caching, not actually using pojoCache directly) is that updates made to the database through the control side should be immediately visible on to the rest of the users. In the past, I've had cache issues that have basically limited me to either pushing all data through the same app, or turning off most of the caching possibilities. The Seam documentation talked at some length about the "rich, multi-layered caching strategy" integrating between the EJB layer, the standard hibernate cache, the conversational cache, impacts on clustering, et cetera, and it seemed to be saying that you got all of that "for free," if you had all data access through the cache, but it sounded more complicated if a 3rd party had to control selective cache expiration. BTW, I agree with your cache comment - I've sped up more than a few apps by removing all custom caching logic completely and just letting the DB do its thing - but that's why I was interested in the idea that if you did everything "The Seam Way" that you got a whole stack of intelligent caching effectively for free, managed completely by the container and framework. Or am I simply reading too much into the caching language, and I'll be just fine? I thought that would at least invalidate Hibernate's potential use of the 2nd level cache. Which might still be okay for the app, but I'm interested in making sure that this is pretty solidly scalable. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4035432#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...