Wicket scalability

[Jan Luehr <ma...@arcor.de>]

Hello,

I'm still trying to get into wicket - this time, I stumbled up on:
http://javathoughts.capesugarbird.com/2008/01/year-of-wicket.html

It says:
"The application was a management console for an enterprise application. It did not require high user traffic, so were weren't concerned about what people talk about as the biggest issue with Wicket, namely scalability. We certainly have had no performance problems ourselves."

Although this article was written some months ago, I didn't notice any concerns refering to scalability.
Do you know, what the author is referring to? 

Thanks,
Keep smiling
yanosz
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org

Re: Wicket scalability

[Jeremy Thomerson <je...@wickettraining.com>]

On Thu, Oct 28, 2010 at 3:54 PM, Jan Luehr <ma...@arcor.de>wrote:

> Hello,
>
> I'm still trying to get into wicket - this time, I stumbled up on:
> http://javathoughts.capesugarbird.com/2008/01/year-of-wicket.html
>
> It says:
> "The application was a management console for an enterprise application. It
> did not require high user traffic, so were weren't concerned about what
> people talk about as the biggest issue with Wicket, namely scalability. We
> certainly have had no performance problems ourselves."
>
> Although this article was written some months ago, I didn't notice any
> concerns refering to scalability.
> Do you know, what the author is referring to?
>

That should be worded "as expected, we did not encounter what people often
cite as a common misconception about Wicket, namely, that it does not scale
well".

People commonly spread FUD about whatever framework doesn't seem to fit
their needs.  The common thing to say about Wicket is that it doesn't scale
well.  They say that holding state in the session kills scalability.
 However, to clarify the simplest: that's wrong, and has been disproven by
numerous examples and benchmarks.  Can you write a Wicket application that
won't scale?  Certainly!  But give me any framework and I'll write you an
application that will crash.  The real question is: can you write a Wicket
application that scales well?  The answer is: ABSOLUTELY!

Here are some really great benchmarks that you may find useful:
http://ptrthomas.wordpress.com/2009/01/14/seam-jsf-vs-wicket-performance-comparison/
http://ptrthomas.wordpress.com/2009/09/14/perfbench-update-tapestry-5-and-grails/

-- 
Jeremy Thomerson
http://wickettraining.com
*Need a CMS for Wicket?  Use Brix! http://brixcms.org*