Is JavaEE dying in the SOA world?

Is JavaEE dying in the SOA world? -- Linux general technology-Linux programming and kernel information. The following is a detailed description. In the next five years, the Java Platform Enterprise Edition (Java EE) will no longer be the mainstream standard programming model, said Richard Monson-Haefel, a senior analyst at the Burton Group, in addition, the development of SOA is one of the reasons for this result.

Last week, the Burton Group experienced a shocking event. Monson-Haefel published a report titled "JEE5: a precursor to the end of Java EE. The Java Platform Enterprise Edition is like a prehistoric animal, because it is too large to rely solely on edible plants to survive and lead to extinction. With the release of spring in JEE5, java Platform Enterprise Edition has become too complex, making it difficult for enterprise-level developers to use it. They are increasingly looking forward to the emergence of alternative versions, such as Ruby-on-Rails.

Monson-Haefel's conclusion is as cruel as a death certificate: "JEE5's failure in complexity indicates that the Java Enterprise Edition platform has finally been defeated in the enterprise development platform field. All enterprises should refer to other platforms when considering new enterprise development, and they should also make preparations in advance to cope with the final demise of Java EE as an enterprise solution ."

The development of the Java Enterprise Edition platform will inevitably follow some of the previous standards, such as the common request proxy system (CORBA). They were also very promising, but they eventually fell short, he said.

"Within five years, the Java Platform Enterprise Edition will become the 21 st Century-based CORBA," Monson-Haefel said. "People will look at it and say, 'It used to be a great time', but because it is too complicated, no one is willing to use it anymore ."

He strives to emphasize that he only reveals the decline of the Java EE platform, and is never a Java language.

"There is no danger to the Java programming language," says the Burton analyst. "I think the Java programming language will continue to grow into a pillar of enterprise-level development in recent years ."

Monson-Haefel is not the only analyst who predicts the failure of the Java EE platform and regards SOA as one of the reasons for this result.

"Java EE is not much time now," said Jason Bloomberg, a senior analyst at ZapThink. He also saw that the culprit of this consequence is the increased complexity of each new version of Java EE. "Obviously, as long as a new version is released or modules are added, the only increase is complexity. Eventually, it will be overwhelmed by itself. From the current perspective, we will not develop more streamlined versions than the existing Java EE ."

Even if we put the complexity aside, when talking about the new era of service-oriented enterprises, Bloomberg, an expert in SOA and Web Services, has seen the Fatal Defects of the Java platform.

"Basically, the world of Java EE is not created for SOA," said ZapThink analyst. "Now, you can rely on the J2EE-based runtime infrastructure to create great SOA implementations in Java and many SOA Implementation products. In fact, Java has many aspects-an object-oriented programming language, a virtual machine infrastructure, and Java EE is a specific framework for implementing the n-layer architecture. Unfortunately, either Java or any virtual machine is not suitable for SOA development platforms ."

The implementation of object-oriented (OO) in Java EE is not fully in line with the core of SOA-oriented services, Bloomberg argues.

"From an object-oriented perspective, services and service instances share the same concept," he said. "The entire set of concepts that an object instance exists independently has little value in SOA ."

Virtual machines in Java EE are not the best solutions for SOA, Bloomberg said.

"Virtual machines aim to enhance code portability, but in SOA, interoperability is more important," he said. "In SOA, if you don't need to move code, why do you need to overcome these difficulties to achieve code porting? Basically, the Virtual Machine of distributed computing implements remote method calling through object serialization, but SOA implements information exchange between services on a fixed interface ."

From Monson-Haefel's point of view, service-oriented makes the need for a unified platform (such as Java EE) irrelevant.

"SOA does reduce the importance of a public program design model," says Burton's analysts. "Because what really matters is not the communication model, but the communication itself. It is the data you are switching. It is a method closely related to your data exchange, rather than the program design model behind the data ."

The main advantage of Java EE is that it provides a public programming model, but this is not the most important when developing SOA. Monson-Haefel said.

"SOA and Web Services reduce the importance of how the backend runs," says Burton's analysts. "The two emphasize how to cooperate with each other, for example, how XML and HTTP of Web services cooperate with each other. It doesn't matter how the background runs ."

Finally, Bloomberg of ZapThink said: enterprise-level JavaBeans/Servlet/Java Server Pages frameworks are inconsistent with SOA.

"You can see that the focus of Java EE is to provide a framework for the upgraded n-layer architecture, which is exactly what large transaction processing websites need," Bloomberg said. "However, if you want to create an enterprise-level framework for SOA, then the construction you want to complete and the construction under the Java EE platform will be quite smooth. The framework you need to create is centered on activation and maintenance of the Service extraction layer, which is crucial for SOA. Therefore, Java EE is very suitable for daily platform-based services, but not SOA ."