<?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: SOA-101: The best 25 minutes you&#8217;ll spend learning about SOA</title>
	<atom:link href="http://grahamis.com/blog/2007/08/25/soa-101/feed/" rel="self" type="application/rss+xml" />
	<link>http://grahamis.com/blog/2007/08/25/soa-101/</link>
	<description>It&#039;s too real to be true</description>
	<lastBuildDate>Sat, 07 May 2011 05:40:39 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: John Senor</title>
		<link>http://grahamis.com/blog/2007/08/25/soa-101/comment-page-1/#comment-400</link>
		<dc:creator>John Senor</dc:creator>
		<pubDate>Fri, 31 Aug 2007 15:49:56 +0000</pubDate>
		<guid isPermaLink="false">http://grahamis.com/blog/2007/08/25/soa-101/#comment-400</guid>
		<description>Incremental SOA is the only practical, cost-effective way to implement SOA. The complexities and costs assoicated with traditional, &#039;top down&#039; architectural implementations do not appeal to today&#039;s business desring agility through SOA. Most IT organizations have been &#039;burned&#039; too many times with &#039;boil the ocean&#039; IT projects which lose sight of their business objects quickly and become &#039;a quest&#039; in and of themselves. Incremental SOA does not mean no sound architecture. it means breaking implementation down into smaller, incremental implementations that &#039;plug and play&#039; into a larger implementation. Such a methodology is infinately scalable, and far less complex to manage.</description>
		<content:encoded><![CDATA[<p>Incremental SOA is the only practical, cost-effective way to implement SOA. The complexities and costs assoicated with traditional, &#8216;top down&#8217; architectural implementations do not appeal to today&#8217;s business desring agility through SOA. Most IT organizations have been &#8216;burned&#8217; too many times with &#8216;boil the ocean&#8217; IT projects which lose sight of their business objects quickly and become &#8216;a quest&#8217; in and of themselves. Incremental SOA does not mean no sound architecture. it means breaking implementation down into smaller, incremental implementations that &#8216;plug and play&#8217; into a larger implementation. Such a methodology is infinately scalable, and far less complex to manage.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Antony Kimber</title>
		<link>http://grahamis.com/blog/2007/08/25/soa-101/comment-page-1/#comment-399</link>
		<dc:creator>Antony Kimber</dc:creator>
		<pubDate>Thu, 30 Aug 2007 12:59:14 +0000</pubDate>
		<guid isPermaLink="false">http://grahamis.com/blog/2007/08/25/soa-101/#comment-399</guid>
		<description>Josh

I like the bit about credible people speaking at the Ark Conference.  If I make a mess of it does that make me incredible?

I enjoyed Jim Webber&#039;s interview and it intrigues me how we can get even looser coupling with MEST.

Antony</description>
		<content:encoded><![CDATA[<p>Josh</p>
<p>I like the bit about credible people speaking at the Ark Conference.  If I make a mess of it does that make me incredible?</p>
<p>I enjoyed Jim Webber&#8217;s interview and it intrigues me how we can get even looser coupling with MEST.</p>
<p>Antony</p>
]]></content:encoded>
	</item>
</channel>
</rss>

