> We are having the potential fun of running a site with around 1 million > users, and a lot more over time. What could be great optimizing points?
Million users per week/ month/ year/ decade? ;-) Answer these questions for yourself: 1) On average, how many concurrent sessions will there be active at any given time? 2) What do you expect might be your peak load in the number of concurrent sessions (and lows might be interesting to know as well)/ what is the maximum number of concurrent sessions you want to support? 3) Do these sessions need to be alive for a long time, or will you e.g. pick them up automatically (e.g. via cookies like many sites do) and keep them short? 4) Is it viable to use sticky sessions? 5) (If 4 == yes) Do you need to support failover? And of just the main session info, or also of (part of) the client's history? Etc. There's a ton more questions to ask, but I'm sure you'll figure that out in the context of your project :-) One of the most important decisions you'll make is what parts of your application (maybe even everything) you'll set up to be stateless and bookmarkable. Keep in mind that even though Wicket is stateful by default, you can build an entire app in a stateless fashion. The drawback to that is that you'll lose some of the OO programming model, but it might still be a nicer programming model than you'd have with many of the model 2 frameworks. Or you can make a mix, like a stateless section for anonymous users and stateful for logged in users. Eelco --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
