Steve Vinoski points to this article about the issues with scaling up SOAP/HTTP. The arguments about HTTP are valid, but I disagree with the conclusions:
- The connection sharing problem seems to be a non-issue for most real-world use-cases — if the client runs on the end users’ computers, I find it hard to believe that someone would argue that HTTP doesn’t scale; if it’s server applications that communicate, I don’t think one would have a need for more simultaneous connections than in the client/server case.
- SOAP is not restricted to use HTTP POST, so optimizations available for GET over HTTP 1.1 are available.
- Finally, I can see the point in using SOAP in conjunction with a reliable transport, such as JMS. But using SOAP over IIOP is probably about as interoperable as rolling your own protocol. But given who’s their employer, it’s not entirely unobvious why the authors suggest it …