Link Details

Finally someone worth a crap said it. Death to SOAP, long live KISS XML.

SOAP and the associated MS-stack must go, but it's a big problem that people think that REST = !SOAP

Most people are going to be happy with a ~working~ (!SOAP) RPC communications system, and would be better off with POX (plain old XML), JSON, or XML-RPC rather than REST, which will be unreliable and slow in many applications.

For instance, if you used REST to implement a banking application in the obvious way, you might implement a transfer by (i) withdrawing from account A, (ii) depositing to account B in two web services call. To do that safely, you need to wrap everything in a distributed transaction, which is a whole lot of trouble.

You ~could~ PUT a document that represents the transfer and do the whole thing in one step, but that's asking a lot from a developer community that still doesn't know what REST is.

Goodbye SOAP and good riddance.

REST isn't the solution for SOAPs complexity...

When I finish dancin' on SOAP's grave can I go shoot WSDL as well?