A couple colleagues of mine here at IONA, Frank Lynch and Mark Fynes, have just published an article over at the WebServices Journal entitled "Where HTTP Fails SOAP." It discusses scalability problems that can arise when applying SOAP/HTTP in the enterprise back end. Given that it seems that many people just assume that SOAP/HTTP is the end-all and be-all of protocols, I think Frank's and Mark's article provides some unique and useful insights into where and why SOAP/HTTP can come up short.
Middleware Matters |
|
Steve Vinoski's Weblog
« Large-scale SOAs? | Main | Freestyle photos »
Where HTTP Fails SOAP
TrackBack
Listed below are links to weblogs that reference Where HTTP Fails SOAP:
» Where HTTP fails SOAP from Brain.Save()
[Read More]
» SOAP/HTTP Scalability from Stefan Tilkov's Random Stuff
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 th... [Read More]
» A transport of delight from XML Nation
[Read More]
Search
About
This page contains a single entry from the blog posted on August 5, 2005 2:26 PM.
The previous post in this blog was Large-scale SOAs?.
The next post in this blog is Freestyle photos.
Many more can be found on the main index page or by looking through the archives.
Powered by
Movable Type 3.31
Movable Type 3.31