Cost of Ownership Analysis: Oracle WebLogic Server vs. JBoss
Join the DZone community and get the full member experience.Join For Free
Below some interesting parts from the whitepaper:
JBoss costs more than WebLogic Server after 2 years and as much as 35% more over 5 years.
- JBoss is 35% more costly than WebLogic Server over 5 years, despite its free license.
- Oracle WebLogic Server becomes less expensive on a TCO basis within two years from acquisition – an advantage that continues to grow with every year of operation.
- Software licensing is a small portion of the total cost of ownership; people costs in operations drive the bulk of long-term costs.
- Other issues, such as performance, time-to-value, and customized infrastructure, can have a significant impact on the overall business ROI of an application server deployment.
Description of Cost Categories Included in Research and Analysis
Description Acquisition This category includes the hard costs for purchase of the application server software and for the hardware platform(s) to run it.
This category includes the labor costs for implementation, installation, configuration, and testing of the application servers and the related infrastructure. Ongoing Application Deployment &amp; Testing Costs This category includes the ongoing labor costs for deploying custom applications from test and staging environments to production environments. It also includes the ongoing interoperability testing and periodic testing for new releases and updates to the application servers and other infrastructure components.
Ongoing Vendor Support Costs
This category includes the hard costs for annual subscription support or maintenance agreements for the application server software, as well as for any additional software required. Ongoing Administration &amp; Management Costs This category includes the ongoing labor costs to configure, manage, and maintain the application servers and the related infrastructure.
Ongoing Monitoring, Diagnostics, & Tuning Costs
This category includes the ongoing labor costs to monitor, tune, and optimize the application servers. Other Cost Considerations This category includes cost considerations identified in the study but not necessarily included in the cost of ownership model. This includes the cost of unplanned downtime, time to market, and backward compatibility considerations.
Table 3 outlines the pro forma costs for a typical application server deployment, consisting of 5 server hosts (server blades with two dual-core processors each), running an average of 4 application server instances per host (one instance per core). The acquisition and on-going costs in Table 3 reflect current list prices for hardware, software and support, less an average discount of 25%, while the people costs for implementation, deployment, testing, administration, and management are based on the results of Crimson’s primary research and resulting cost model.
- JBoss implementation costs more than twice as much as WebLogic Server implementation.
- By the end of the implementation phase, the cost of JBoss (inclusive of acquisition cost) is within 33% of the cost of WebLogic Server and operations haven’t started yet.
- Though we haven’t tried to quantify the business cost of the delay in time-to-value associated with an extra 8.5 weeks of effort, it could clearly be substantial.
Check the whitepaper for more like Ongoing Operations which involve:
- Application Deployment and Infrastructure Testing Costs
- Application Server Administration, Management, Monitoring, and Tuning Costs
- Monitoring, Diagnostics, and Tuning Costs.
- “Out-of-the-box” configuration and implementation tools are more mature, robust, and efficient for WebLogic Server than for JBoss, with the result that time-to-value is faster, the customization needs lower, and the costs lesser than with JBoss.
- Similarly, out-of-the-box administration, management, and tuning tools have been through as many development cycles as the core software and are consequently more complete and more productive than their equivalents in the JBoss environment.
- Oracle takes on the responsibilities and costs of maintaining performance and backwards-integration as the software evolves; users of JBoss take on those responsibilities for themselves.
Published at DZone with permission of Spyros Doulgeridis, DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.