This post originated from an RSS feed registered with Agile Buzz
by James Robertson.
Original Post: Whoa - J2EE application suckage
Feed Title: Cincom Smalltalk Blog - Smalltalk with Rants
Feed URL: http://www.cincomsmalltalk.com/rssBlog/rssBlogView.xml
Feed Description: James Robertson comments on Cincom Smalltalk, the Smalltalk development community, and IT trends and issues in general.
Following the herd doesn't seem to be working out for a lot of people. The .NET Guy links to a Java Lobby post on the uptime and performance statistics of J2EE services:
The bottom line is that way too many of the J2EE applications deployed in enterprises today have absolutely dismal performance. To put it bluntly, our applications stink! You can completely forget all the haughty talk about "five nines" reliability. The average availability of the J2EE applications referenced in the survey is just 88%. That's right - we're talking the fabled "five eights" of J2EE availability. Half of the responses show overall app availability (an application's ability to service user requests) below 96%, which means almost seven hours of downtime per week! That's seven hours of pain, lost revenue, confusion, and bad news for Java. Not only that, but half the responses are indicating even less than 96% availability.
This is the logical result of running with a new technology - with staff that did not have time to learn it - and rushing to eliminate the existing (i.e., working) infrastructure in favor of the new stuff. Add in the overwhelming complexity of J2EE, and these numbers are not terribly surprising. Kind of makes you wonder whether the various analysts that have pushed their customers to move to J2EE have any credibility at all. Makes me wonder if J2EE is a solution in search of a problem...
Previous Topic
