In case you missed it, there is an infographic based on research from IDC that IDC and Red Hat released, nicely illustrating the business value of Red Hat JBoss Enterprise Application Platform 6.
A picture is already worth a thousand words, so I don’t need to spend too much time trying to improve on the infographic. (Just the numbers on ROI and annual IT staff productivity increases tell a pretty decent story.)
There is more to that EAP 6 story than in the infographic alone. IDC had done a similar whitepaper a couple of years before the infographic and executive summary, and it had broke down three customer examples of how, exeactly, JBoss EAP 6 had achieved its business value for them. The first example was of a medium-sized bank that was already running an older version of JBoss EAP. When they were evaluating JBoss EAP 4 versus JBoss EAP 6, the newer version had substantial improvements:
- Their internal performance testing showed an improvement of 3.5 times.
- Startup times for applications were reduced by almost half.
- Because of a newer Java EE standard, application development and complexity was reduced. The bank was planning on increasing their application delivery cycles by 25% (from four times per year to five).
The one thing that was a background consideration in those customer stories was the migration process itself. The banking customer slated over 12 months, from testing to production rollout, for upgrading its systems.
Partially, this was due to the seismic shift in architecture between JBoss EAP 4 and JBoss EAP 6. JBoss EAP was completely redesigned. In JBoss EAP 5, the product had moved to being very functionality-rich, but it came at the price of more complexity. (That’s a topic for another day.) JBoss EAP 6 was re-architected so that it could retain its rich functionality and technology, but in a way that was more consumable and more valuable to developers. But that lead to a disconnect between JBoss EAP 4 and JBoss EAP 6.
That kind of world-shifting change is not going to happen again in JBoss EAP 7. In a recent conversation with John Doyle (the product manager for JBoss EAP 6, among other middleware products) said that in his opinion, one of the most valuable and unsung features of JBoss EAP 7 was its attention to interoperability and backwards compatibility with JBoss EAP 6.
JBoss EAP 6 is the framework (technologically and metaphorically) for JBoss EAP 7. With the business case for JBoss EAP 6, a lot of the drivers of those benefits are being expanded in JBoss EAP 7 — things like graceful shutdowns, improved startup times, better classloading performance, better web server performance. But one of the better benefits may be that it will be easier to realize those benefits — because JBoss EAP 7 was designed with migration in mind.