Best Architecture choice for my web application

[manifoldronin]

Hello,

I have a medium sized web application which currently runs in tomcat. I'm looking at clustering to give me fail over and load balance. I could just go ahead and cluster it as is but as more functionalty comes along the application is starting to look a bit big and clumsey.

So, from a requirement standpoint, which level of availability are you looking for? In other words, can your users afford losing their ongoing sessions, but can log back in right away, if one of the server fails? If that's the case, then you don't really need the expensive session replicating clustering, which would take a heavy toll on many aspects of your system.

[karldmoore]

So, from a requirement standpoint, which level of availability are you looking for? In other words, can your users afford losing their ongoing sessions, but can log back in right away, if one of the server fails? If that's the case, then you don't really need the expensive session replicating clustering, which would take a heavy toll on many aspects of your system.

Thats a very good point, I thought this had already been brought up. On second read I see nobody picked up on this before. Totally agree, if you can possibly do without it you should.