You're correct that SOAP is protocol independent (even SOAP 1.1 allows multiple transports), but the only formally defined SOAP binding is for HTTP. Also note that the WS-I Basic Profile requires use of HTTP. My advice is to follow the WS-I Basic Profile unless you have very strong justification to make an exception for a specific application. The bottom line is that if you want to ensure multi-vendor interoperability, you should use HTTP.
There are issues associated with using HTTP, though. They are:
Quite a few companies address these issues by using a MOM protocol, such as WebSphere MQ. The issues associated with using a MOM protocol, though, are:
Dig Deeper on Service-oriented architecture (SOA)
Related Q&A from Anne Thomas Manes
Anne Thomas Manes explains the differences between open source clients and open source implementations. Continue Reading
Anne Thomas Manes discusses the best way to go about creating an enterprise data dictionary and why the systems works well. Continue Reading
Anne Thomas Manes explains the difference between 'hard' real time and 'live' real time systems. Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.