we primarily develop internal-facing (i.e. non-public) Seam apps with less than 100 user base.
is it worth the time/effort to design/implement Hibernate 2nd level cache with these Seam apps?
This article is very helpful: http://solutionsfit.com/blog/2009/04/06/second-level-caching-still-an-effective-performance-tuning-technique/
We also have a 2 node horz JBoss cluster in prod with state replication turned off (yes, no seamless failover). Not sure if that matters when you're evaluating/designing 2nd level cache. thx.
Retrieving data ...