Take the 2-minute tour ×
Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. It's 100% free, no registration required.

Considering that more and more Web Services are implementing a RESTful interface, I am wondering what the future of SOAP will be?

I'm looking for any kind of papers, statistics, articles or publications from official sources (e.g. books, articles and journals) which provide information on the future of SOAP.

Thanks in advance!

share

migration rejected from stackoverflow.com Aug 5 '13 at 17:15

This question came from our site for professional and enthusiast programmers. Votes, comments, and answers are locked due to the question being closed here, but it may be eligible for editing and reopening on the site where it originated.

closed as primarily opinion-based by gnat, Corbin March, Jimmy Hoffa, Dan Pichelman, psr Aug 5 '13 at 17:15

Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise.If this question can be reworded to fit the rules in the help center, please edit the question.

    
I edited the tone of the question, to prevent the question from being closed. –  Pindatjuh Aug 1 '11 at 10:39
5  
"the future of SOAP". Predictions of the future are very, very expensive. I prefer PayPal as a way to fund my predictions of the future. The more you pay, the more accurate I can be. –  S.Lott Aug 1 '11 at 14:13
1  
They aren't really competing technologies. If you need the features of SOAP and the WS-* implementations then you should use those. If you don't, you should use REST. See this Q for more:programmers.stackexchange.com/questions/23386/… –  Jeremy Aug 1 '11 at 15:29

4 Answers 4

It is a protocol that is in the wild with a wide variety of supporting services, devices and toolkits. At the very least lots of already built things are going to continue to support SOAP until it becomes painful not to. Which could be well beyond our lifetimes.

share

You're going to have to deal with both SOAP and JSON for a long long time. As @WyattBarnett said, "... well beyond our lifetimes." (We hope!)

share

Once a RESTful service can provide all of the features available in SOAP, or once those features are no longer necessary, then SOAP will slowly cease to be used.

share
    
REST can provide all the features of SOAP already –  Tom Squires Aug 1 '11 at 15:36
1  
Utter nonsense. Start with the fact that REST is not a protocol, just an architectural style. –  John Saunders Aug 1 '11 at 15:37
3  
Anything which requires the use of a protocol. –  John Saunders Aug 1 '11 at 15:42
2  
So the HTTP that supports REST is what? Not a protocol? –  S.Lott Aug 1 '11 at 21:58
2  
I don't think it follows that because X can provide all the features of Y, or features of X are no longer required, that Y will become dominant and X obsolete. There are lots of "obsolete" protocols and languages that are still in use today with no sign of ever going away. C is still used even after C++ (and C++ still around despite Java and C#) and POP is still around after IMAP etc. –  Dan Diplo Aug 2 '11 at 7:50

Considering there are plenty of companys still working with asp classic (the last company i worked for) soap will definatly still be about for a very long time. It may be depreciated a lot quicker than that though.

Personaly I find soap to be a very complicated solution to quite a simple problem. REST is so much more elegent and flexible

share

Not the answer you're looking for? Browse other questions tagged or ask your own question.