I wrote about SOAP vs REST a few weeks ago. Today I noticed this article with a presentation about putting together Rails REST services with ActiveResource.
Recently it seems like the SOAP vs REST debate is heating up. Most of the debate seems to be leaning toward convincing people to not use SOAP based on its increasing complexity. Different people have different views on what REST is but in general if you look at the SOAP specifications or SOAP Standards and Web services and then look at the REST specification, REST for the Rest of Us, or REST you see that in general there is a lot more complexity to SOAP and that is just SOAP itself and not any of its extensions. Here are some good articles I've found that should give you insight into the debate:
- REST vs HTTP+POX vs SOAP – A simple explanation of REST and SOAP.
- How I Explained REST to My Wife – Another simple explication of what REST is.
- The S Stands for Simple – A conversation that expresses the issues with using SOAP.
- REST for Web Services – The outline for a new REST for web services book.
- The REST Dialogues – A set of fictional dialogs on REST vs SOAP.
- The REST Dialogues, A Real eBay Architect – A response to "The REST Dialogues" by a real eBay architect.
- 85% of Amazon calls are to REST version of their API
- Google turns off SOAP API
- Why SOAP sucks
After looking over the above references you may be interested in looking at Programmable Web's API list and see what others are using. The majority of the public services listed offer REST interfaces with some offering both REST and SOAP and very few offer just SOAP. Even though REST seems to be in favor now I believe there are still plenty of areas where SOAP makes sense when you have resources to devote to feeding and caring for it.