Comment Re:If they... (Score 1) 97
The automagic part is a bit spooky when it comes to data shared among threads. If you have large reporting systems that share big data caches in the jvm, but that can process in multiple threads, doesn't this data have to get copied between all nodes needing it over the network? Seems like this could be a good solution for applications that are compute but not data intensive, and that don't require many shared resources.
We have one the biggest, most complicated java based web delivered applications on the internet, but our solution is to remove common state from the application processing machines-- they are stateless number crunchers. State (common data) is maintained in nodular cluster databases. Application load is easily distributed using load balancing in front of the application servers based on parameters like cpu and other resource load ( we use mod_athena from http://ath.sourceforge.net/ ). You can farm out to commodity systems this way.
Mark Wolgemuth, Production Architect
Employease, Inc. ( www.employease.com )
We have one the biggest, most complicated java based web delivered applications on the internet, but our solution is to remove common state from the application processing machines-- they are stateless number crunchers. State (common data) is maintained in nodular cluster databases. Application load is easily distributed using load balancing in front of the application servers based on parameters like cpu and other resource load ( we use mod_athena from http://ath.sourceforge.net/ ). You can farm out to commodity systems this way.
Mark Wolgemuth, Production Architect
Employease, Inc. ( www.employease.com )
