Sunday, March 25, 2007
REST is the Betamax of Web Services
I while ago I blogged about REST. I was pretty excited about it at the time, it seemed to blow away a lot of the lava layers that have been accumulating around the SOAP protocol with a back to basics, or rather back to HTML approach that leverages a lot of the forgotten functionality of that protocol. OK, so should I be using it when my customers ask me to implement a Service Oriented Architecture? I think the answer has to be no. SOAP has gained far too much market share in the developer tools community. Especially in the Microsoft world, I’d be throwing away all the SOAP support built into the MS toolset and the .NET framework in particular that makes implementing web services with SOAP so easy. Also I’d be loosing any interoperability with other platforms, because with a RESTfull approach you’re basically designing your own protocol. It’s a shame, but sometimes you just have to go with the flow.
Of course the world of IT (actually the world generally) is full Betamaxes. If the best tools always won, we’d be programming in Haskell, on BeOS running on a RISC machine.
Subscribe to:
Post Comments (Atom)
Posts
4 comments:
REST is not dead....check out WOA, which is emerging as best practice from experience of implementing SOAs
Thanks jo and dave. I have to admit that that post was entirely from the perspective of a Microsoft Mort (me) and largely reflects that kind of view. I'm willing to be persuaded and I've just ordered a copy of RESTful Web Services by Leonard Richardson in order to educate myself better.
Oh how wrong I was :)
I'm not sure I understand to be honest. It's precisely the contrary. It's about embracing an infrastructure that is already there and has proven to work.
Post a Comment