Goodbye, Java EE?

Goodbye, Java EE?

Summary: Prediction: 'In five years, Java EE will be the CORBA of the 21st Century.'

TOPICS: Software

Rich Seeley surfaced a report from Burton Group's Richard Monson-Haefel in which the analyst uncategorically states that Java Enterprise Edition is destined for the ash heap of history.

Monson-Haefel predicts that "In five years, Java EE will be the CORBA of the 21st Century. People will look at it and say, 'It had its time but nobody uses it any more because it was too complicated.'" He predicts that the Java programming language itself will continue to survive, but the Java EE framework is too complicated, and that developers are opting for more lightweight and easier to deploy frameworks such as Ruby on Rails.

"JEE5's failure to address complexity is a harbinger of the Java EE platforms' fall from dominance in the enterprise development platform arena. Organizations should look elsewhere when considering new enterprise development and should plan for the eventual sunset of Java EE as an enterprise solution."

Seeley also quotes ZapThink's Jason Bloomberg, who agreed with Monson-Haefel's assessment, stating that Java EE "will collapse under its own weight," and pointed out that there are far simpler ways to build SOAs:

"The Java EE world is fundamentally not built for SOA. Now, you can build perfectly good SOA implementations on Java and many of the SOA implementations in production today depend on their J2EE-based runtime infrastructure. In fact, Java is many things – an object-oriented programming language, a virtual machine infrastructure and the Java EE flavor of Java is specifically a framework for implementing n-tier architectures. Unfortunately, none of these facets of Java, or any other virtual machine-based, object-oriented runtime environment for that matter, are ideally suited as a platform for SOA."                 

"SOA and Web services diminished the importance of what you have running on the backend," Burton's Monson-Haefel said. "They emphasize how you interface with each other, which is XML and HTTP for Web services, for instance. What's running behind the scenes is really less important."

A couple of thoughts here: Yes, CORBA is super-complicated, but there are still a lot of fully functioning CORBA implementations out there in the enterprise world. And, agreed that Java EE can also get pretty complicated, but implementations sit at the core of many newer implementations -- from large commercial vendors such as IBM and BEA, as well as open source platforms such as Apache and JBoss.

Java EE is not for the faint-hearted, and not even for power end-users seeking to rapidly deploy just-in-time applications for their particular business needs of the moment. The framework is intended for enterprise development shops, with all the high-transaction and high-scalability requirements that go with it. Plus, at this point, there is a tremendous skills base built up around Java EE. Yes, other simpler, more rapid application development frameworks probably will eventually become more popular, but Java EE isn't likely to go away anytime soon, and this all has the familiar ring of years of predictions of the mainframe's impending demise.

Of course, ultimately, in the scheme of all things SOA, it really doesn't even matter what happens to Java EE. The beauty of SOA is that it does not favor one particular platform or approach -- it doesn't matter if services come out of Java EE, .NET, Ruby on Rails, CORBA, or even COBOL. 

Topic: Software

Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.


Log in or register to join the discussion
  • vacuous crap ...

    it's hardly worth commenting on this sort of report other than to denounce it
  • Practically unlikely

    Do you think those companies like IBM,Oracle and others who are making huge invenstments in J2EE platform based applications simply throw those away in five years ? Not at all.

  • Where's the beef?!

    Just aother rant from the guy who brought us things from the very first books about J2EE (that recently seems to have declined in sales) up to terribly flawed benchmark sponsored by Microsoft, where he tried to show that .net is faster than a broken j2ee-application (broken by the master himself...).

    But what exactly is Monson-Haefel trying to tell us? In five years from now, almost any platform will have vanished, so what's his point? Does he even bring an argument, except the mantra, that JEE 5 is complicated? This mantra seems to have replaced the mantra "Java is slow" that haunted java the last 10 years...

    Even worse is his argument, that SOA makes it irrelevant wether the app is coded in .net or jee or ruby or whatever - very true, but in the end you'll have to choose on of these to actually implement the services your SOA promised to offer - so again, what does this argument have to do with JEE vs. .net vs. whatever?

    Shame on me, that I even was attracted by the headline, I should have known better. I really would have liked to see some arguments - has it become worse or better with jee5 since j2ee, is there a requirement that other platforms fullfill that jee does not, are there requirements fullfilled in jee that are not needed anymore? And if things are compllicated, are they complicated with a reason, or is sun&the jcp so stupid that they cannot make things easier?! I would have liked an opinion on these topics, not another microsoft sponsored marketing-blabla.
  • Delusional

    SOA is an architectural concept, while JEE5 is a specific platform which can be used in an SOA implementation. In light of that, saying that the former will kill ther later does not make much sense.

    You should have spent more time on the trenches, that would have helped giving the impression that you knew what you were talking about...Maybe then you would have noticed that J2EE is a major SOA enabler for many organizations...

    Articles like these are just a way to create FUD in the minds of the clueless, of which there seem to be plenty in the corporate world.
  • Maybe

    I think being a analyst in the IT-realm is the hardest job one can imagine. It's unpredictible.
    So maybe Monson-Haefel is right.
    I made a small cartoon: