Grab some REST with your SOAP


Become An Insider

Sign up now and get free access to hundreds of Insider articles, guides, reviews, interviews, blogs, and other premium content from the best tech brands on the Internet: CIO, CSO, Computerworld, InfoWorld, IT World and Network World Learn more.

It's not one protocol vs. another -- they're both needed in the enterprise. Here's why.

A bit of rest always helps. We have to seize every opportunity to pause and reflect on where we've been before making new plans to move forward. In the topsy-turvy world of SOA (Service-Oriented Architecture), which has now become one of the foundations of enterprise architecture, a bit of introspection goes a long way toward building greater robustness into the business applications on top.

Although the term SOA was coined in 1994 by Gartner Group's Alexander Pasik, SOA and related technologies didn't become mainstream pieces of enterprise architecture until around 10 years later. Some would say SOA still hasn't reached its full potential in the enterprise.

But even before there was SOA there were Web services. And behind the ecosystem of Web services was a protocol called SOAP, which at one time used to be an acronym for Simple Object Access Protocol. (With the newest SOAP specification from the World Wide Web Consortium -- version 1.2, which came out in 2003 -- SOAP is now supposed to be called just SOAP; it is no longer an acronym.)

To continue reading, please begin the free registration process or sign in to your Insider account by entering your email address:
Rip and replace: When it pays to make a total systems change
View Comments
You Might Like
Join the discussion
Be the first to comment on this article. Our Commenting Policies