Win a copy of Functional Reactive Programming this week in the Other Languages forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Automatically load-balancing a Wicket application

 
Riyad Kalla
MyEclipse Support
Ranch Hand
Posts: 75
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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.
 
Eelco Hillenius
author
Ranch Hand
Posts: 37
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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
Posts: 12
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic