3 ms·
There isn't anything specifically wrong with SOAP and for some applications it's still the right choice. As with everything "use the right tool for the job", w
by mindcrime 8y ago
There isn't anything specifically wrong with SOAP and for some applications it's still the right choice. As with everything "use the right tool for the job", whether it's SOAP, REST, DCOM, GraphQL, CORBA, ONC RPC, Thrift, DCE, RMI, Avro, or $SOMETHING_ELSE.
That said, I think two major things gave SOAP a bad name and caused people to look to alternatives in many situations:
1. Lack of interoperability between major implementations. One of the whole selling points of SOAP was that you should be able to implement a SOAP service on, say, an IBM S/360 running COBOL, and then consume that service from a VB app running on Windows 2000, in an app that also consumes a SOAP API written in Java running on a Solar box. In reality, issues in the various implementations - whether intentional or otherwise - made it far harder to achieve that lofty goal than it should have been. That was especially true early on. Things got better over time, but that really dinged SOAP and the whole WS-* stack in the eyes of may people.
2. The performance overhead due to XML (both the parsing, and the raw message size due to XML being a little bit verbose).
Arguably a 3rd factor was the apparent complexity of things like XML namespaces and XML schema, although I personally think that factor is a little over-stated. Namespaces and schemas aren't actually all that hard to understand.
Anyway, this industry tends to be very faddish and once JSON came along and became the next big shiny thing that got rid of the verbosity of XML, along with schemas and namespaces, everybody suddenly jumped on the XML-RPC bandwagon and, later, REST.
- mindcrime 8y ago... a Solar box. That should, of course, read "... a Solaris box".