Hi there, I am evaluating Seam and trying to get the examples running. (Quite an exercise to get Seam 1.2.1 working on JBoss 4.2.1!!!...put this module in, remove that jar, tweak this tweak that...).
In booking example it says, "Keeping conversational state in memory in the middle tier is a great way to improve your application's scalability." Further, it says that the search functionality is backed by stateful session bean and that bean caches the results of the search. Now, my question is this: We have an app that will be accessed by about 50000 people, about 1000 will be simultaneous users hitting the server. How well can this approach of creating stateful session beans scale? From what we understand is stateful SBs don't scale that well and on top of it Seam suggests to caches such data is SBs. Some performance experts suggest to not cache such data at all and rely on database chaching. Any thoughts on this? (BTW, password rules for registering on this site suck big time!!! What is it a credit card processing company???) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4082056#4082056 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4082056 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
