If it's about getting your wicket application to support huge loads,
it's mainly not wicket thats the problem but what else you use,
hibernate, spring etc.. But all these things can be solved by using
caches...
Only thing I find missing with caching with wicket would be something
like a prepending keyword strategy to be able for a cache to distinguish
easy what you can cache and what not.
[1]=http://www.nabble.com/Dynamic-PrependKeywordEncodingStrategy--%28making-a-simple-rule-for-caching-with-apache%29-td19006754.html#a19006754
Martijn Dashorst wrote:
Fabulously40.com survives digg.com effects.
LasVegas.com is also Wicket based (or at least parts of it)
finan.nl doesn't have a public application, but their Wicket web based
solution will be used inside major banks *world wide*.
Sounds like me that these companies are able to make Wicket work on a big scale.
There is also a german based travel agency that has deployed 20-30
sites based on one Wicket code base iirc.
It also depends on what you call enterprise application...
Vocus is a SaaS solution for high schools in the Netherlands. Though
250-300 concurrent users isn't that much of a scaling problem, we do
need to handle 120K-200K requests per day. It is quite an intensively
used application, with a very broad functionality base.
Martijn
On Mon, Aug 18, 2008 at 12:01 PM, Michael Mosmann <[EMAIL PROTECTED]> wrote:
Hi,
Can anyone tell me an example of an enterprise application developed
with wicket? In an discussion some people said, that they think, that
wicket is not suited for enterprise scaled applications. "what you see,
is what you believe" could solve this problem.
thanks
Michael Mosmann
--
-Wicket for love
Nino Martinez Wael
Java Specialist @ Jayway DK
http://www.jayway.dk
+45 2936 7684
