<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: REST vs. WS-*: A Parable</title>
	<atom:link href="http://cafe.elharo.com/web/rest-vs-soap-a-parable/feed/" rel="self" type="application/rss+xml" />
	<link>http://cafe.elharo.com/web/rest-vs-soap-a-parable/</link>
	<description>Longer than a blog; shorter than a book</description>
	<lastBuildDate>Tue, 09 Mar 2010 18:31:23 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: FAQ about Web Services and Related Technologies &#124; Program Creek</title>
		<link>http://cafe.elharo.com/web/rest-vs-soap-a-parable/comment-page-1/#comment-360620</link>
		<dc:creator>FAQ about Web Services and Related Technologies &#124; Program Creek</dc:creator>
		<pubDate>Wed, 25 Feb 2009 23:34:14 +0000</pubDate>
		<guid isPermaLink="false">http://cafe.elharo.com/web/rest-vs-soap-a-parable/#comment-360620</guid>
		<description>[...] REST vs. WS-*: A Parable by Elliotte Rusty Harold [...]</description>
		<content:encoded><![CDATA[<p>[...] REST vs. WS-*: A Parable by Elliotte Rusty Harold [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mokka mit Schlag &#187; REST Pessimists</title>
		<link>http://cafe.elharo.com/web/rest-vs-soap-a-parable/comment-page-1/#comment-34460</link>
		<dc:creator>Mokka mit Schlag &#187; REST Pessimists</dc:creator>
		<pubDate>Sun, 03 Dec 2006 12:55:43 +0000</pubDate>
		<guid isPermaLink="false">http://cafe.elharo.com/web/rest-vs-soap-a-parable/#comment-34460</guid>
		<description>[...] Several people have started to push back on the REST vs. WS-* and RELAX vs. W3C XSD and Rails vs. JEE fronts with a self-defeating argument. Well, of course, you&#8217;re right they say; but it doesn&#8217;t matter. The big vendors are selling these big, expensive complex solutions; and that&#8217;s all the CIO hears; so that&#8217;s all that matters. Sure, you can get the job done better/faster/cheaper with Rails/REST/RELAX, but you won&#8217;t. Well, to these pessimists I have a one-word response: [...]</description>
		<content:encoded><![CDATA[<p>[...] Several people have started to push back on the REST vs. WS-* and RELAX vs. W3C XSD and Rails vs. JEE fronts with a self-defeating argument. Well, of course, you&#8217;re right they say; but it doesn&#8217;t matter. The big vendors are selling these big, expensive complex solutions; and that&#8217;s all the CIO hears; so that&#8217;s all that matters. Sure, you can get the job done better/faster/cheaper with Rails/REST/RELAX, but you won&#8217;t. Well, to these pessimists I have a one-word response: [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Practical Guile &#187; A Story of REST vs WS-*</title>
		<link>http://cafe.elharo.com/web/rest-vs-soap-a-parable/comment-page-1/#comment-921</link>
		<dc:creator>Practical Guile &#187; A Story of REST vs WS-*</dc:creator>
		<pubDate>Mon, 22 May 2006 02:02:38 +0000</pubDate>
		<guid isPermaLink="false">http://cafe.elharo.com/web/rest-vs-soap-a-parable/#comment-921</guid>
		<description>[...] Elliotte Rusty Harold has an entertaining story of REST and WS-* in the real world. One that involves air-conditioners. It wouldn&#8217;t take a genius to see that he&#8217;s in favour of RESTful interfaces as opposed to using Web Services. Personally, I haven&#8217;t had much experience with the implementation of external services using either, so it was a humorous read at least. [...]</description>
		<content:encoded><![CDATA[<p>[...] Elliotte Rusty Harold has an entertaining story of REST and WS-* in the real world. One that involves air-conditioners. It wouldn&#8217;t take a genius to see that he&#8217;s in favour of RESTful interfaces as opposed to using Web Services. Personally, I haven&#8217;t had much experience with the implementation of external services using either, so it was a humorous read at least. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Poulin</title>
		<link>http://cafe.elharo.com/web/rest-vs-soap-a-parable/comment-page-1/#comment-780</link>
		<dc:creator>Michael Poulin</dc:creator>
		<pubDate>Sat, 20 May 2006 13:15:44 +0000</pubDate>
		<guid isPermaLink="false">http://cafe.elharo.com/web/rest-vs-soap-a-parable/#comment-780</guid>
		<description>[...no precedence for SOA in the area I work. At first this seemed like a disadvantage. I now appreciate the option to completely avoid SOAP RPC]

Hey guys, who but marketing said that SOA requires anything like SOAP RPC? It is the most primitive and speculative approach to use SOAP RPC and call it SOA. If we talk about Web Services, I care about WSDL only. SOAP or REST are just transport/protocol models for SOA, which can easily stand on IIOP, for example. A crowd of RPC or message calls is as far from SOA as relational model far from OO.

To me, the easier protocol the better. However, please, make it standard - mandatory for all. If you can do it with REST, I am for it. Otherwise, sorry...</description>
		<content:encoded><![CDATA[<p>[...no precedence for SOA in the area I work. At first this seemed like a disadvantage. I now appreciate the option to completely avoid SOAP RPC]</p>
<p>Hey guys, who but marketing said that SOA requires anything like SOAP RPC? It is the most primitive and speculative approach to use SOAP RPC and call it SOA. If we talk about Web Services, I care about WSDL only. SOAP or REST are just transport/protocol models for SOA, which can easily stand on IIOP, for example. A crowd of RPC or message calls is as far from SOA as relational model far from OO.</p>
<p>To me, the easier protocol the better. However, please, make it standard &#8211; mandatory for all. If you can do it with REST, I am for it. Otherwise, sorry&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The Cave &#187; Blog Archive &#187; REST vs. WS-*: A Parable</title>
		<link>http://cafe.elharo.com/web/rest-vs-soap-a-parable/comment-page-1/#comment-657</link>
		<dc:creator>The Cave &#187; Blog Archive &#187; REST vs. WS-*: A Parable</dc:creator>
		<pubDate>Fri, 19 May 2006 08:11:40 +0000</pubDate>
		<guid isPermaLink="false">http://cafe.elharo.com/web/rest-vs-soap-a-parable/#comment-657</guid>
		<description>[...] Very amusing. [...]</description>
		<content:encoded><![CDATA[<p>[...] Very amusing. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Soft-dev: mainly about software development &#187; Representational State Transfer</title>
		<link>http://cafe.elharo.com/web/rest-vs-soap-a-parable/comment-page-1/#comment-449</link>
		<dc:creator>Soft-dev: mainly about software development &#187; Representational State Transfer</dc:creator>
		<pubDate>Fri, 12 May 2006 14:15:23 +0000</pubDate>
		<guid isPermaLink="false">http://cafe.elharo.com/web/rest-vs-soap-a-parable/#comment-449</guid>
		<description>[...] More discussion [...]</description>
		<content:encoded><![CDATA[<p>[...] More discussion [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: think</title>
		<link>http://cafe.elharo.com/web/rest-vs-soap-a-parable/comment-page-1/#comment-447</link>
		<dc:creator>think</dc:creator>
		<pubDate>Fri, 12 May 2006 13:16:08 +0000</pubDate>
		<guid isPermaLink="false">http://cafe.elharo.com/web/rest-vs-soap-a-parable/#comment-447</guid>
		<description>&lt;strong&gt;A breath of fresh air&lt;/strong&gt;

Thanks, Andrew at Digital Earth Weblog for today&#039;s entry. I&#039;ve been noticing lately a bit of a discussion about REST vs. WS-* that&#039;s been going on.
</description>
		<content:encoded><![CDATA[<p><strong>A breath of fresh air</strong></p>
<p>Thanks, Andrew at Digital Earth Weblog for today&#8217;s entry. I&#8217;ve been noticing lately a bit of a discussion about REST vs. WS-* that&#8217;s been going on.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Digital Earth Weblog &#187; Blog Archive &#187; Web Services Humour - A Parable</title>
		<link>http://cafe.elharo.com/web/rest-vs-soap-a-parable/comment-page-1/#comment-443</link>
		<dc:creator>Digital Earth Weblog &#187; Blog Archive &#187; Web Services Humour - A Parable</dc:creator>
		<pubDate>Fri, 12 May 2006 06:52:41 +0000</pubDate>
		<guid isPermaLink="false">http://cafe.elharo.com/web/rest-vs-soap-a-parable/#comment-443</guid>
		<description>[...] REST vs. WS-*: A Parable [...]</description>
		<content:encoded><![CDATA[<p>[...] REST vs. WS-*: A Parable [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The Web 2.0 Place</title>
		<link>http://cafe.elharo.com/web/rest-vs-soap-a-parable/comment-page-1/#comment-440</link>
		<dc:creator>The Web 2.0 Place</dc:creator>
		<pubDate>Fri, 12 May 2006 04:09:02 +0000</pubDate>
		<guid isPermaLink="false">http://cafe.elharo.com/web/rest-vs-soap-a-parable/#comment-440</guid>
		<description>&lt;strong&gt;Mandatory reading on WebServices&lt;/strong&gt;

Every now and then some voice of reason raises up above the hype hypnotised crowd and offers the chance for awakening to the ones that have not been completely brain washed. </description>
		<content:encoded><![CDATA[<p><strong>Mandatory reading on WebServices</strong></p>
<p>Every now and then some voice of reason raises up above the hype hypnotised crowd and offers the chance for awakening to the ones that have not been completely brain washed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Edmon Begoli</title>
		<link>http://cafe.elharo.com/web/rest-vs-soap-a-parable/comment-page-1/#comment-439</link>
		<dc:creator>Edmon Begoli</dc:creator>
		<pubDate>Fri, 12 May 2006 03:35:31 +0000</pubDate>
		<guid isPermaLink="false">http://cafe.elharo.com/web/rest-vs-soap-a-parable/#comment-439</guid>
		<description>I actually do not think that this is a match of any kind.

I&#039;ve done both styles of AC systems on multi-million even a billion dollar project and I am yet to see where 
simple REST is less useful than standardize-everything, interoperability-with-everything WS-* stuff.

The biggest champions of WS-* are the vendors like IBM who sold you some billion dollars big iron thirty years ago and now instead of helping you to migrate to a more nimble, future proof platform they are selling you a 
&#039;pig on a lipstick&#039; WS-* friendly, ESB solutions that will make your COBOL/CICS based iron run forever.

Just buy 100 million WebSphere ESB bus and everything will be just fine ...  Just keep putting wrapper, over wrapper ...

REST in this case is really selling you a different model. Instead of selling you a SOAPey story of ultra-interoperability and standardization it is giving you the value what good old webservices 
were meant to provide you. Location independence, simplicity, universality.

I do not care if eBay&#039;s webservices are WS-* compliant as long as they are easy to learn, easy to use, performant and if they add value to my electronic business.

Isn&#039;t that the formula behind every technology that successfully took off.</description>
		<content:encoded><![CDATA[<p>I actually do not think that this is a match of any kind.</p>
<p>I&#8217;ve done both styles of AC systems on multi-million even a billion dollar project and I am yet to see where<br />
simple REST is less useful than standardize-everything, interoperability-with-everything WS-* stuff.</p>
<p>The biggest champions of WS-* are the vendors like IBM who sold you some billion dollars big iron thirty years ago and now instead of helping you to migrate to a more nimble, future proof platform they are selling you a<br />
&#8216;pig on a lipstick&#8217; WS-* friendly, ESB solutions that will make your COBOL/CICS based iron run forever.</p>
<p>Just buy 100 million WebSphere ESB bus and everything will be just fine &#8230;  Just keep putting wrapper, over wrapper &#8230;</p>
<p>REST in this case is really selling you a different model. Instead of selling you a SOAPey story of ultra-interoperability and standardization it is giving you the value what good old webservices<br />
were meant to provide you. Location independence, simplicity, universality.</p>
<p>I do not care if eBay&#8217;s webservices are WS-* compliant as long as they are easy to learn, easy to use, performant and if they add value to my electronic business.</p>
<p>Isn&#8217;t that the formula behind every technology that successfully took off.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
