Although the debate between session replication vs stateless can't be definitively solved and depends on the application, I'd like to hear about your experiences with both. How are you designing your current applications, and what implications has the choice that you might not have expected - would you do anything differently if you could?
I ask because I'm still unsure about whether to decrease memory usage by increasing database usage (or bandwidth usage if sending state back to the client) by going stateless at the application tier. Stateless Are there any people using stateless application tiers with transactions that are inherently stateful, such as wizard-type screens or other business processes or workflows? How'd that turn out? Did you choose to move this state to the client (through cookies) or to the database? Session replication For session replication in Tomcat 6, what's the ideal replication group size in general? Would you ever want to set it to more than 2 instances? (Because for any more, then you'd have a lot more overhead in transferring state back and forth to even more other instances...) With session replication between 2 machines, are you effectively reducing the capacity of each server, at least in terms of memory, by 50%? Hopefully I'm looking at it the wrong way, because it not, I'm not really liking the session replication idea if I'm decreasing hardware usage by half. Thanks. -- View this message in context: http://www.nabble.com/-OT--Session-replication-vs-stateless-tf4325727.html#a12319704 Sent from the Tomcat - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
