CodeFutures News & Industry Commentary Blog

Friday, December 22, 2006

Enterprise Java Moving in Three Strategic Directions

J2EE used to the only real option for developing for enterprise applications in Java. The market has moved on and David Chappell has written an excellent article on the future of enterprise Java and the three directions it is going.

The three directions of Java are:

J2EE, now branded JEE, is going to continue. It will not be the core product offering of many vendors any more. This is partly because JEE is often perceived as not ideal for SOA (not an unfair claim, given that it was not designed from scratch for SOA).

David Chappell explains the situation very well: It was never reasonable to expect powerful vendors like IBM and BEA to remain Sun’s vassals, especially now that their J2EE market share vastly exceeds that of their putative lord. Combine this with Sun’s reluctance to give up control, and the result should surprise no one: the Sun-led J2EE alliance is at an end.

The OSOA, with Service Component Architect and Service Data Objects, will take over from the JCP as the focus of the major vendors' next wave of products.

Open Source application development products are now highly credible and will continue to thrive. The list of successful open source products is impressive, including Linux, Eclipse, Struts, Tomcat, MySQL, and several more. In fact, the only area where open source is weak is SOA, which of course is the focus the Open SOA.

As David Chappell major risk with the divisions in Java is that it will not be as strong as it might be if the roadmap was unified. However, with JEE and the JCP not serving the commercial interests of the major Java vendors like BEA and IBM and JEE not perfectly aligned with SOA, there is no option but to move forward with the Open SOA.

PJ Murray
CodeFutures Software


Tuesday, December 19, 2006

Forrester on SCA

Forrester Research has just published a new SCA report on called "SCA Slowly Gathers Steam".

The report abstract appears to be rather understated regarding how fast SCA will be used in real projects:

In November 2005, IBM and BEA Systems formed the Open Service Oriented Architecture (OSOA) collaboration, with the intent to define a language-neutral service-oriented architecture (SOA)-centric programming model. Service component architecture (SCA) is a set of specifications that intend to promote interoperability and simplify assembling composite applications. Significant progress has been made on SCA specifications, but development tool and application server support is still evolving and there is limited support by SOA infrastructure vendors. Architects and developers will see milestone releases of tooling and runtimes that support SCA in the first half of 2007 but they should not expect to execute mission-critical projects using SCA compliant tools or runtimes before the end of 2007.

Interestingly, there is no mention of the Service Data Object specification.

PJ Murray
CodeFutures Software