Based on a detailed analysis of how customers typically deploy enterprise Java applications, we have developed a model that examines the TCO implications of moving to a hypervisor-based virtualization platform.
The model allows you to compare the potential TCO savings associated with several architectures for running enterprise Java applications: Non-Virtualized, where applications run on dedicated hardware; the Virtualized OS model, with multiple virtual machines all running traditional operating system-/Java Virtual Machine/application-server software stacks; and the new BEA LiquidVM™ architecture, which allows Java applications to run in virtual machines with no operating system.
Taking into account key physical, operational support, hardware and software data center costs, we are able to build a picture of the true cost of ownership of large-scale Java applications over a period of 1-5 years. The underlying model uses your data for power, labour, space, hardware and software costs to allow you to explore detailed cost breakdowns associated with moving to a virtualized infrastructure platform. Test a variety of different hardware scenarios, application instance/server ratios and target server consolidation metrics and view 3-year TCO estimates, broken down to show the relative costs associated with Data Center Real Estate, Power and Cooling, Unplanned Server Downtime, Software Administration, Software and Hardware License costs.
We believe you'll find this analysis a valuable guide to what virtualization really means for IT organizations running enterprise Java applications. To find out more, just contact BEA and arrange for a free TCO Workshop with one of our Java virtualization specialists. We would be happy to help you build a detailed model, based on your application needs, cost structures, and plans, to guide your thinking about the enterprise Java virtualization's real TCO potential.