If you are not sure whether you will end up with 100 or 100'000 users... Well, I would try do design the system with "clustering" in my mind. Then I could throw more hardware at it, without too much problems. Seems that even Tomcat 5 is capable of clustering nowadays, so it should not even be a problem of money.
"Clustering in my mind": If its just for scalability, then try to avoid applicaiton-wide caches. If its also for fail-over: then you have to watch your session size. hth Alexander -----Original Message----- From: Ashu Jaiswal [mailto:[EMAIL PROTECTED] Sent: Freitag, 11. Juni 2004 17:49 To: [EMAIL PROTECTED] Subject: Re: Struts scalability and benchmarking What if the system needed to scale to thousands (or potentially even millions) of user? Would just throwing more hardware solve the scalability issues? I know this sounds really open ended, but I'm just trying to figure out how well struts has performed (or will) in the past for large websites. The FAQ seems to have the "struts powered website" link missing. thanks, Ashu Subject: Re: Struts scalability and benchmarking From: Bill Siggelkow <[EMAIL PROTECTED]> Date: Thu, 10 Jun 2004 17:23:37 -0400 To: [EMAIL PROTECTED] Personally, I think this would be more a function of (1) the application server/container that you are using (Tomcat/JBoss/WAS/...) and (2) the hardware/clustering etc. Also, you need to do some additional analysis on expected number of users, estimate how much data will be held in the session, what database you are using, blah blah Ashu Jaiswal wrote: > Hi, > Just wondering if there have been any scalability and benchmarking > studies done on struts. I am trying to figure out if struts would scale > out well if the number of users in a system grew rapidly, starting from > a small user base. > > I would appreciate any comments, suggestions or pointers. > > thanks, > Ashu --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
