<?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: Are Developers Hurting SOA?</title>
	<atom:link href="http://blog.dragonsoft.us/2008/02/14/are-developers-hurting-soa/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.dragonsoft.us/2008/02/14/are-developers-hurting-soa/</link>
	<description>Talk about Technologies, Software Architecture and Management</description>
	<lastBuildDate>Tue, 31 Jan 2012 01:41:22 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Serge Dosyukov</title>
		<link>http://blog.dragonsoft.us/2008/02/14/are-developers-hurting-soa/comment-page-1/#comment-8141</link>
		<dc:creator>Serge Dosyukov</dc:creator>
		<pubDate>Thu, 14 Feb 2008 19:35:41 +0000</pubDate>
		<guid isPermaLink="false">http://blog.dragonsoft.us/2008/02/14/are-developers-hurting-soa/#comment-8141</guid>
		<description>There is truth in your saying. But opposite perception about SOA is as valid.
It all comes to implementation of the abstract idea and how much of it is taken in the proposed architecture.
SOA gives you an abstract concept with almost no specific boundaries defined per se. Now, how it fits your product concept/architecture, it is a different story.
Also, please notice that we are not discussing a validity of the SOA model but rather acceptance of such by both parties - developers and managers.
David&#039;s point was that Developers do not want to accept/consider SOA model when Managers do (for what ever reasons applicable).
My point was that acceptance of the SOA is nothing to do with developers therefore they have no way of &quot;hurting&quot; it more then anyone else.
</description>
		<content:encoded><![CDATA[<p>There is truth in your saying. But opposite perception about SOA is as valid.<br />
It all comes to implementation of the abstract idea and how much of it is taken in the proposed architecture.<br />
SOA gives you an abstract concept with almost no specific boundaries defined per se. Now, how it fits your product concept/architecture, it is a different story.</p>
<p>Also, please notice that we are not discussing a validity of the SOA model but rather acceptance of such by both parties &#8211; developers and managers.<br />
David&#8217;s point was that Developers do not want to accept/consider SOA model when Managers do (for what ever reasons applicable).</p>
<p>My point was that acceptance of the SOA is nothing to do with developers therefore they have no way of &#8220;hurting&#8221; it more then anyone else.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Xepol</title>
		<link>http://blog.dragonsoft.us/2008/02/14/are-developers-hurting-soa/comment-page-1/#comment-8140</link>
		<dc:creator>Xepol</dc:creator>
		<pubDate>Thu, 14 Feb 2008 19:15:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.dragonsoft.us/2008/02/14/are-developers-hurting-soa/#comment-8140</guid>
		<description>Let&#039;s be honest.  Even if you are interested in SOA, the sales pitch of &quot;We&#039;d like to use code we have no control over, running on a service we have no controller over, only available over a connection that isn&#039;t 100% reliable and comes with no assurance it will be there tommorow and no recourse if it isn&#039;t in a mission critical role&quot;  is a damn tough sell.
Show me the manager or client that will say &#039;sign me up for that&#039;.
SOA is a fundamentally flawed concept that only grew based on is &quot;coolness&quot; factor.  Cool tho it might be, building your code based upon it is too much like building a house on sand.  If you need the house to be there tommorow, chances are you aren&#039;t going to run the risk.</description>
		<content:encoded><![CDATA[<p>Let&#8217;s be honest.  Even if you are interested in SOA, the sales pitch of &#8220;We&#8217;d like to use code we have no control over, running on a service we have no controller over, only available over a connection that isn&#8217;t 100% reliable and comes with no assurance it will be there tommorow and no recourse if it isn&#8217;t in a mission critical role&#8221;  is a damn tough sell.</p>
<p>Show me the manager or client that will say &#8216;sign me up for that&#8217;.</p>
<p>SOA is a fundamentally flawed concept that only grew based on is &#8220;coolness&#8221; factor.  Cool tho it might be, building your code based upon it is too much like building a house on sand.  If you need the house to be there tommorow, chances are you aren&#8217;t going to run the risk.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

