A call to arms.
It’s that bad.
The REST / Web Arch. crowd falls back to its secret weapon in the fight for mankind: The Dialogue.
What I think success means with regards to “Web Services”.
It has nothing to do with the web.
The loyal opposition is growing in weird ways.
Some thoughts on AMQ, the latest solution to all your problems.
Praise for Yahoo! as they launch an initial set of web style APIs.
A theory on why big vendors, big analyst houses, and the tech press want to sell you the worst possible solutions to your problems.
It’s not a robot thing.
Adam Bosworth joins the Loyal WS-Opposition – minus the loyal part, perhaps.
“We (the RESTafarians) are not stubborn zealots. We’re just right. Sorry :–)”
“… Rails has picked a side in the SOAP vs REST debate. Unless you absolutely have to use SOAP for integration purposes, we strongly discourage you from doing so. As a naturally extension of that, we’ve pulled ActionWebService from the default bundle.”
RESOLVED FIXED
“Should machine-to-machine, multi-hop, RESTful communications expose a need for additional functionality, then, and only then, will the need be addressed. This is opposed to the WS style of standards creation where solutions are created that go in search
Wow, I'm flattered blush Turns out I do know something about SOA after all. Speaking of “Motherhood and Apple Pie” – I quite liked that essay but it was one of those that never really took off.
Nice bit of history showing the chain of events that led to WS-*.
Extremely clear and right take on REST, WS, and other techniques for distributing systems.
Wonderfully done.
“Jim Gray reminded me that TerraServer does offer SOAP interfaces. And yet those interfaces demonstrably have not inspired a flurry of innovation. Why not?”
Greg Beaver talks about some of the benefits of REST based design as he’s moving PEAR from XML-RPC to standrad HTTP/URIs/XML.
Koranteng ponders how it is possible for REST based systems to kick so much ass.
How cool is that?
I didn’t know SOAP/WS systems were so capable. Astounding!
That’s because they don’t have shithead analyst speculation driving feature development…
Just for fun :)
Udell wishes REST and WS-* could get along… The REST people did too – two or three years ago (e.g. Prescod, Baker).
Google reflects on some of the decisions made for the AdWords API.
Paul Prescod gives some background and opinion on the REST/SOAP debate.
More people coming over to the loyal opposition…
Carlos Perez with a nice wrap up of recent WS-* vs. REST discussion around the blogosphere.
More reports of shrinking WS-* mindshare and cries for tools for building REST based architecture.
Complexity is kryptonite to interoperability. It’s that simple.
Oh, this is brilliant. Look at the bright side, Mark, at least it’s horribly useless in a way that’s interoperable!
:) “… it isn’t about REST or SOAP or WS-* or .NET or Java or whatever, it’s about easy.” — Tim Bray
… there has been a recent round of “glowing reviews from analysts”. What could possible go wrong?
Mark Nottingham wondering why WS-Transfer (HTTP wrapped up in SOAP wrapped up in HTTP bwhhahaha) didn’t get more heat from the opposition.
A big list of problems with the current WS stack. Contains pointers to mailing-list discussion on various issues.
Simon St. Laurent noticing the recent WS-Opposition.
Sean McGrath backing Tim Bray on the Loyal WS-Opposition.
The legs the Loyal WS-Opposition is standing on. (Tim Bray)
Joe Gregorio on Tim Bray’s “The Loyal WS-Opposition” post. This might end up being a real committee or something.
Tim Bray on WS-Sanity: “So here’s what I’m going to do. I’m going to stay out of the way and watch the WS-visionaries and WS-dreamers and WS-evangelists go ahead and WS-build their WS-future.”