Java Virtualization for Server Consolidation 97
Steve Wilson writes "Cassatt Corporation has released new software that enables administrators with large J2EE farms to much more efficiently use their resources. In order to do this, it leverages the virtualization capabilities inherent in the JVM to create a single shared pool of hardware resources which which all J2EE applications can draw."
Re:Sweet (Score:4, Interesting)
In theory, it would work across OS platforms. Considering that the guy hired a bunch of N1 [sun.com] engineers to do this, I don't see why they'd change the design.
Of course, practically it depends on how this software works. It's possible to write software that's tied to a given OS, even in Java.
cJVM (Score:4, Interesting)
Sounds awefully like clustering JVM. One thing I am not sure is that;
1. failover is done by manager node?
2. application distribution over what stack? shared pool doesn't necessarily mean shared memory space.
3. parrallel or distributed processing or session clustering?
The more I think about it, this company sounds like a hype. $100,000 for 40 node pool and $5K per node is a bit of stretch in anyone's pocket in my opinion.
What if your data center is full? (Score:4, Interesting)
In that case it's smarter to spend $100k on a product that can reportedly reduce server use by a factor of five, and make room for new applications to run on the same boxes you already have.
There are a number of complexities to this which mean it's not something you'd want to roll on your own, not if you wanted it to be stable anyway. And from the sounds of it since it's targeted at specific application servers (just Weblogic for now) it also has hooks into that system as well. To me the price seemed about right for a large company.
Re:TBH (Score:2, Interesting)
Back on topic, I suppose this might be useful for companies with peak loads in various applications occurring at different times but it looks rather expensive. They must have done their market research though, so good luck to them.
Re:Sweet (Score:5, Interesting)
Now on to my own question.
Steve, the one thing I'm not getting from the article, nor from the website [cassatt.com] (at least, I haven't seen it yet) is as follows: Is this just another DRMAA [wikipedia.org] implementation, or is it more than that? If it is, could you give us a good overview of why it's better than N1? If not, can you explain what exactly this software does for a company? It somewhat sounds like it makes a single JVM run across multiple machines as if they were one, but if that's the case, how does it work? Is it a customized JVM based on Sun source code?
Thanks in advance!
Here's a Translation (Score:4, Interesting)
We use various technologies to allow us to efficiently and safely run more of your J2EE applications on fewer physical servers. By using fewer servers, but still maintaining your performance and availability characteristics, you can save a lot of money running your data center.
Does that help?
-Steve
Steve Wilson
Cassatt Corporation
http://www.cassatt.com/ [cassatt.com]
Distributed JVM (Score:3, Interesting)
Re:Sweet (Score:3, Interesting)
This question, far more than one about the absolute cost of Cassatt's solution, is the one that will decide whether I choose Sun N1, Cassatt, or whether I choose to build out my data centers so that each app has dedicated hardware. After all, the $5k per server costs would cover probably 1-3 months of the total costs in the real world of running a server; if I can eliminate those costs, $5k/year is a bargain.