On 16 jul 2008, at 09:54, Nino Saturnino Martinez Vazquez Wael wrote:
Daan van Etten wrote:
On 16 jul 2008, at 04:49, Ryan Sonnek wrote:
On Tue, Jul 15, 2008 at 8:54 AM, Nino Saturnino Martinez Vazquez
Wael <
[EMAIL PROTECTED]> wrote:
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?
[..]
Cache, Cache, Cache. if you're running any high volume/traffic
sites, you
absolutely need to leverage caching to get any amount of
scalability. This
goes for ANY web framework and not just wicket.
readup on some of the published whitepapers for high traffic sites
(flickr
is a great case study) to see how they do it.
Try to have the server-side as stateless as possible. If the state
is at the client, any server can handle the requests without
exchanging state. See http://cwiki.apache.org/WICKET/stateless-pages.html
for a short intro. It will change the way you write your project,
but keeping state server-side can be disastrous for real performance.
Yeah I know, problem are that our application are ajax heavy, and
stateless and ajax does not cope well I've heard..
Maybe not within Wicket, I know too little of Wicket to draw a valid
conclusion on that. But it is definitely possible.
Look for example at the SproutCore development model. They create
their application in Javascript and do requests to the backend to get
records, save records, etc. Their application runs in the browser,
making the server more like a stateless backend (from what I
understood of SproutCore).
I know it's possible (and done before) to build a Javascript
application (or even desktop) that way.
Regards,
Daan van Etten
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
