One of the most natural options-Evaluation of BEA's acquisition of Kodo JDO/ejb3 Products

Today, the biggest news in the J2EE industry is Bea's acquisition of solarmetric, which develops Kodo JDO/ejb3 persistence products. The first instinct to see this message is that this is the most natural choice Bea can make. This also means that the era of ejb3 has arrived.

The transition from J2EE 1.4 to 5 is a huge change. The transformation from the heavy ejb2 model to the ejb3 of the IOC/pojo model is a huge change. It can be said that it is a Nirvana and rebirth of EJB technology. The technical specifications and implementations can both be said to be the re-engineering of the Orthodox J2EE architecture, especially the persistence layer Entity Bean (which is also the best part of EJB technology in the past ), in the past, ejb2 was a completely different development model, which is closer to the development community, making it easier and better in performance.

For this and the ejb3 development platform market that will be created, various traditional J2EE vendors will naturally look at it. However, it is not easy to break out in a new round of competition. Due to the huge transformation from ejb2 to ejb3 technology, developing an ejb3 container is not simply improving the existing ejb2 container concept, but re-developing a container, the technical threshold/workload is huge. The development of an ejb3 container consists of two parts: the development of the container itself and the development of the pojo-based persistence layer. It takes one to two years for any part to start from development to stable operation. Without a certain amount of technical accumulation, the time will be longer.

It is interesting to see the order in which ejb3 products appear. In the U.S. market, the order is JBoss, Oracle, And kodo.

JBoss was the first to launch its own well-known pojo persistence product hiberante. It can be said that it has accumulated the deepest Technological accumulation, not to mention that the ejb3 specification has learned a lot about the implementation of hibernate. Therefore, it is not surprising that JBoss can quickly launch ejb3 products. In addition, as a leader in the J2EE market and a relatively small company, JBoss also needs to take the lead in technology and compete with Bea/IBM's veteran J2EE vendors.

Oracle has never had much improvement in the J2EE market, but Oracle has the oldest pojo persistence product toplink. In the ejb2 age, oralce was unable to sing the ghost scene of pojo. Now there is a bit of salted fish back to life. oralce, relying on toplink's technical accumulation, also quickly launched the ejb3 server product and became the leader in ejb3 specifications together with JBoss.

It turns around in the world, and Bea, a technological pioneer in J2EE, lags behind in this ejb3 battle. Although EJB containers are Bea's strengths, without the accumulation of pojo persistence product development experience, Bea lags behind JBoss/oracle in the ejb3 race. Redeveloping a pojo persistence layer and integrating it into ejb3 containers is a long process. From the market point of view, Bea's one-year lag behind other J2EE vendors is unacceptable, and neither shareholders nor faces can be met. Therefore, the acquisition of Kodo JDO/ejb3, that is, Bea, will be able to make the most natural choice. It is foreseeable that Bea will launch ejb3 in the first quarter of next year.

The two-year-old pojo product provides a standard melee. The US market saw the result today. It is clear that we were somewhat idealistic about the wild-looking situation. Small and medium-sized companies with innovative pojo development experience and accumulation have been merged by established companies. JBoss has compiled Hibernate and versant has compiled jdogenie. BEA has compiled Kodo and IBM has compiled geromino (not ejb3 ). The world is getting more and more calm. The Giants are still giants and have mastered standards and cutting-edge technologies. The only thing that is still out of the traditional J2EE scope is that it cannot be spring. It is foreseeable that it is also a matter of time.

For J2EE vendors in China, if the ejb2 era and foreign products are still poor, ejb3 products will be inferior. The competition gap will widen. The domestic J2EE Middleware vendors are under greater pressure. As the only vendor of ejb3 persistent products in China, we started to cooperate with other domestic J2EE vendors to Promote the Development of Domestic j2ee5 (ejb3) middleware, but will we still have time before the next-generation J2EE platform competition?