I am seeing a lot of new web services are implemented using a REST style architecture these days rather than a SOAP one.
what is the difference?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I am seeing a lot of new web services are implemented using a REST style architecture these days rather than a SOAP one.
what is the difference?
There is no such thing as one being better, they are different and what is better depends on your needs.
If you need a lot of standards based functionality with relatively rich clients SOAP will deliver that. It gives thinks like metadata, WSDL, security or reliable messaging to name but a few through the WS-* specs. It is also transport agnostic and completely XML centric.The flip side of the coin is that there is a big standard that is not always implemented in an interopable fashion.
REST on the other hand is all about HTTP and its way of doing things. Very flexible and allows any kind of data format you like. So not just XML but also SOAP, images or VCards to name a few. It embraces the web standards so will work with almost any programming stack. The flip side is far fewer standards so it can be much harder to figure out how to do something.