Comments on: Our vision of Java/.NET interoperability http://www.jnbridge.com/jn/blog/2009/11/12/our-vision-of-java-net-interoperability/ Java and .NET Interoperability Tue, 04 Oct 2011 13:21:13 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: Tony Baer http://www.jnbridge.com/jn/blog/2009/11/12/our-vision-of-java-net-interoperability/comment-page-1/#comment-18516 Tony Baer Fri, 13 Nov 2009 17:27:43 +0000 http://www.jnbridge.com/blog/?p=88#comment-18516 I would certainly concur that web services is not synonymous with Java/.NET interoperability. The web services stack form of SOA is itself a fairly complex buffer tier arhcitecture that has its own interoperabity issues. That said, SOA, whether it be web services or looser RESTful architecture, makes sense where the connection should be more loosely coupled. That is, where the source or target systems for the transaction are likely to change or be replaced by other systems or applications. On the other hand, if we are talking about a dedicated, foundational transaction where the connections are not likely to change and where performance considerations ar paramount, there is no substitute for direct transactional interoperability. I would certainly concur that web services is not synonymous with Java/.NET interoperability. The web services stack form of SOA is itself a fairly complex buffer tier arhcitecture that has its own interoperabity issues.

That said, SOA, whether it be web services or looser RESTful architecture, makes sense where the connection should be more loosely coupled. That is, where the source or target systems for the transaction are likely to change or be replaced by other systems or applications. On the other hand, if we are talking about a dedicated, foundational transaction where the connections are not likely to change and where performance considerations ar paramount, there is no substitute for direct transactional interoperability.

]]>