"In six years, systems interop has become dramatically simpler and easier, and SOAP and WSDL have made that possible. Despite the massive adoption of SOAP, there are other protocols, and that will always be the case. Innovation and evolution breeds specialization and heterogeneity.

"REST, using XML or not, is often cited as an alternative to SOAP. True enough, but this a distinction without a difference. Does it really matter if there are angle brackets or curly braces on the wire?

"The key requirements are: it-just-works interoperability between systems, productivity and power with the development and management tools, and flexibility or "future proofing" in the programming frameworks.

"These are the tenets supported by Microsoft's integration infrastructure, including Windows Communication Foundation (WCF), the high-performance programming framework for communications; and BizTalk Server, the process engine and integration hub. These pieces remain constant regardless of how you decide to employ SOAP, REST or some other system-specific protocol.

"Where are the opportunities for improvement in today's integration technologies? There are several, but given current trajectory, service registry is an important area. Today, IT manages multiple repositories: a code repository for developers, a systems repository for systems managers, a project repository for project managers. SOA initiatives may add a service repository to the mix.

"Converging or federating these disparate systems, and exposing this information to stakeholders in all phases of the IT system lifecycle—project managers, architects, developers, business analysts, compliance managers, security officers, systems administrators and so on—will spur the next great jump in business productivity and agility. This convergence is a key part of the vision behind Microsoft's forthcoming 'Oslo' wave of products.

"SOAP, WSDL, WS-*, and UDDI are proven and widely adopted, and REST is growing strongly. Building upon that base, the next evolution of this infrastructure will bring even more value."

And there you have it. 'nuff said!

If you haven't read the other article, compare Martin's view to that of MuleSource's Dan Diephouse, who said, "The unholy trinity of SOAP, WSDL and UDDI needs to go." Then let us know in the comments who has the right of it.