So, let's bash the JVM.
It's rigid. It's non-elastic. It's fixed in its limited size. It can't dynamically scale up or down. It's heavily constrained by the OS.
It's inefficient. It's unstable under a heavy load. It's garbage collection process can freeze the system for ten to fifteen non-stop seconds at the most inconvenient of times, and the only way to avoid this is by configuring small JVMs with a minimal amount of memory allotted to them (4 gigs?). Get yourself a server with a few terabytes of memory, and you've got an unmanageable number of JVMs configured to eat all of that up. And it even gets worse if you're supporting your own private cloud.
But there is a solution. It's an Azul solution. You see, the big brains at Azul have put a zinger of a solution together that will help you virtualize your Java runtime, and avoid those nasty problems associated with running Java based applications on massive pieces of hardware. And what's the solution called? Well, it's called Zing.
With Zing, you can virtualize your environment, allowing you to elastically scale your applications up and down; with Zing, you can now effectively use that massive chunk of hardware that's currently hosting a million little JVMs; and of course, all of this greatly simplifies the process of deployment and configuration.
There's a few pieces to the Zing puzzle. You've got a Zing Virtual Machine that does your transparent virtualization. There're the Zing Virtual Appliances that provide you with elastic and scalable capacity, there's the Zing Resource Controller, which provides management and monitoring facilities, and finally, there's the Zing Vision, which is a built in application profiling tool.
Here are just a few of the reasons why Zing will be making a big splash in the Java industry in the next little while:
•An Optimized Runtime Platform
?More effective use of resources (10s of cores, 100s of GBs)
?Scales smoothly over a wide range (from 1 GB to 1 TB)
?Greater stability, resiliency and operating range
?Completely eliminates GC-related barriers
?Practical support for 100x larger heaps (e.g. 200-500+ GBs)
?Sustain 100x higher throughput and allocation rates
•Simplified Java App Deployments
?Better app stability with fewer, more robust JVMs
?Zero-overhead runtime visibility ?Application-aware resource control
You can find out more by reading Azul's press release: