Comments on: Microsoft absent from open standards movement around SOA http://www.fastforwardblog.com/2007/06/20/microsoft-absent-from-open-standards-movement-around-soa/ Wed, 07 Jan 2009 11:43:57 +0000 http://wordpress.org/?v=2.7 hourly 1 By: Ron http://www.fastforwardblog.com/2007/06/20/microsoft-absent-from-open-standards-movement-around-soa/comment-page-1/#comment-49485 Ron Mon, 17 Sep 2007 20:39:53 +0000 http://fastforwardblog.com/2007/06/20/microsoft-absent-from-open-standards-movement-around-soa/#comment-49485 I believe David Chappell (the consultant, not the Oracle VP) had it right when he characterized SCA/SDO as a schism in the Java EE vendor world. For Microsoft this must look like a delightful thing, as IBM attempts to rewrite major parts of Java EE outside of the Java Community Process, and thus outside of Sun's control. The ultimate goal of the main vendors behind SCA (IBM, SAP, Oracle, BEA)? To weaken enterprise application portability in Java. That right folks, it's good old vendor lock-in, just like Microsoft always tries to exercise. It was time to stop customers from changing app servers, or even using app servers from different vendors concurrently. Tough on the direct sales force, and very tough on IBM global services. Vendor lock-in is a natural choice for vendors who don't have interoperability built into their DNA. Will Microsoft benefit from this step backwards in the Java community? Probably not, since it really doesn't give MS an opening into Java shops that plays to MS's strengths. They could possibly create enough FUD to loosen a few accounts. Joining SCA/SDO would only put their own proprietary collection of technologies at risk, without tangible reward for MS. Either way, don't count on MS feeling left out, and choosing to join the SCA party at either OSOA.ORG or OASIS CSA. I believe David Chappell (the consultant, not the Oracle VP) had it right when he characterized SCA/SDO as a schism in the Java EE vendor world. For Microsoft this must look like a delightful thing, as IBM attempts to rewrite major parts of Java EE outside of the Java Community Process, and thus outside of Sun’s control.

The ultimate goal of the main vendors behind SCA (IBM, SAP, Oracle, BEA)? To weaken enterprise application portability in Java. That right folks, it’s good old vendor lock-in, just like Microsoft always tries to exercise. It was time to stop customers from changing app servers, or even using app servers from different vendors concurrently. Tough on the direct sales force, and very tough on IBM global services. Vendor lock-in is a natural choice for vendors who don’t have interoperability built into their DNA.

Will Microsoft benefit from this step backwards in the Java community? Probably not, since it really doesn’t give MS an opening into Java shops that plays to MS’s strengths. They could possibly create enough FUD to loosen a few accounts. Joining SCA/SDO would only put their own proprietary collection of technologies at risk, without tangible reward for MS.

Either way, don’t count on MS feeling left out, and choosing to join the SCA party at either OSOA.ORG or OASIS CSA.

]]> By: Benjy http://www.fastforwardblog.com/2007/06/20/microsoft-absent-from-open-standards-movement-around-soa/comment-page-1/#comment-18225 Benjy Sat, 23 Jun 2007 12:31:00 +0000 http://fastforwardblog.com/2007/06/20/microsoft-absent-from-open-standards-movement-around-soa/#comment-18225 I disagree. Microsoft has already made great strides forward in interoperabilty and configurable service deployment with WCF and i dont think them supporting SCA is of any benefit at all. As long as they are interoperable with other SOA implementations why does it matter ? COM and DCOM werent interoperable with CORBA but thats not the case for WCF. As far as SDO is concerned, well ADO.NET vNext and all the stuff they are coming up with around the EntityFramework are good enough. Besides, i dont think the Java camp really has much ground to stand on. look what happened to JDO. Great idea. Shot down in flames because the vendors were worried they would lose control and be unable to lock their customers down to their particular stacks. Look at JBI. Purports to do the same kind of thing as WCF but what happened there? Lets see some real interoperable implementations of SCA and SDO from the Java big guys without them trying to backbite each other or buy each other up and then see how interoperable MS is with them. Benjy I disagree. Microsoft has already made great strides forward in interoperabilty and configurable service deployment with WCF and i dont think them supporting SCA is of any benefit at all. As long as they are interoperable with other SOA implementations why does it matter ? COM and DCOM werent interoperable with CORBA but thats not the case for WCF.
As far as SDO is concerned, well ADO.NET vNext and all the stuff they are coming up with around the EntityFramework are good enough.

Besides, i dont think the Java camp really has much ground to stand on. look what happened to JDO. Great idea. Shot down in flames because the vendors were worried they would lose control and be unable to lock their customers down to their particular stacks. Look at JBI. Purports to do the same kind of thing as WCF but what happened there? Lets see some real interoperable implementations of SCA and SDO from the Java big guys without them trying to backbite each other or buy each other up and then see how interoperable MS is with them.

Benjy

]]>