This week's giveaway is in the Android forum.
We're giving away four copies of Android Security Essentials Live Lessons and have Godfrey Nolan on-line!
See this thread for details.
The moose likes Other Application Frameworks and the fly likes Automatically load-balancing a Wicket application Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Android Security Essentials Live Lessons this week in the Android forum!
JavaRanch » Java Forums » Frameworks » Other Application Frameworks
Bookmark "Automatically load-balancing a Wicket application" Watch "Automatically load-balancing a Wicket application" New topic
Author

Automatically load-balancing a Wicket application

Riyad Kalla
MyEclipse Support
Ranch Hand

Joined: Jul 30, 2007
Posts: 75
Guys I've been using Thoof since it launched, which IIRC is a Wicket app. One thing I noticed is that the site's story-submission process is always pretty slow, I don't know if that is by design or not, but it made me wonder what it would take to load-balance a Wicket app easily.

It seems to me that the ejb-esque nature of Wicket with it's models (detached,reattach, etc.) would allow it to be load-balanced, atleast by designer, more easily than other apps.

Any input on this subject or core design elements to pay special attention to from the get-go?

BTW: I think the whole "model" idea you went with in Wicket was conceptually and implementation-wise one of my favorite things about it. It is a really awesome mechanism by which to handle heavy objects.


Riyad
Eelco Hillenius
author
Ranch Hand

Joined: Apr 23, 2008
Posts: 37
Originally posted by Riyad Kalla:
Guys I've been using Thoof since it launched, which IIRC is a Wicket app. One thing I noticed is that the site's story-submission process is always pretty slow, I don't know if that is by design or not, but it made me wonder what it would take to load-balance a Wicket app easily.


As far as I know, Thoof runs on a Tomcat cluster with full replication and a few nodes. It might be slow because they limit the hardware they use.

Originally posted by Riyad Kalla:

It seems to me that the ejb-esque nature of Wicket with it's models (detached,reattach, etc.) would allow it to be load-balanced, atleast by designer, more easily than other apps.

Any input on this subject or core design elements to pay special attention to from the get-go?


Wicket is a stateful framework, and state is kept in the server. That's a disadvantage for clustering, because if you'll have to replicate that state (sessions and pages) if you want failover. Luckily, it's not a new problem, and several solutions exist. Regular session replication works, Terracotta works, and you can find an optimized solution based on Tribes (Tomcat) here as a wicket-stuff project.

For more info, the best place to be for such questions are the Wicket mailing lists.

Regards,

Eelco
Jonathan Locke
Greenhorn

Joined: Mar 11, 2004
Posts: 12
Yes. Thoof ran out of money for hardware long ago. You can read this blog post:

http://blog.thoof.com/index.php/geekery/build-to-scale-our-web-architecture/

about our scalability.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Automatically load-balancing a Wicket application
 
Similar Threads
Need suggestion regarding java framework for web portal development
Wicket In Action: Best fit for small web applications?
Recommendations to make Web development as easy as possible
Webframework to choose?
Wicket, TDD, evolutionary design