<?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 in &#8216;09: Dead, alive or in search of new meaning?</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/eye-on-oracle/soa-in-09-dead-alive-or-in-search-of-new-meaning/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/eye-on-oracle/soa-in-09-dead-alive-or-in-search-of-new-meaning/</link>
	<description>A SearchOracle.com blog</description>
	<lastBuildDate>Thu, 24 Jan 2013 12:22:23 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: osymad</title>
		<link>http://itknowledgeexchange.techtarget.com/eye-on-oracle/soa-in-09-dead-alive-or-in-search-of-new-meaning/#comment-1385</link>
		<dc:creator>osymad</dc:creator>
		<pubDate>Sat, 24 Jan 2009 17:54:07 +0000</pubDate>
		<guid isPermaLink="false">http://eyeonoracle.blogs.techtarget.com/2009/01/19/soa-in-09-dead-alive-or-in-search-of-new-meaning/#comment-1385</guid>
		<description><![CDATA[Architecture still being white elephant, i think SOA will change this 2009 to bring us a better (currently does not exists) integration between Customer requirements... but not only functional ones even business needs like deliveries, milestones and some other administrative contraints to build a quality architecture design. By the other hand SOA must be standarize its concepts to avoid misunderstanding between &quot;Architects&quot; , business analyst programmers and developers.]]></description>
		<content:encoded><![CDATA[<p>Architecture still being white elephant, i think SOA will change this 2009 to bring us a better (currently does not exists) integration between Customer requirements&#8230; but not only functional ones even business needs like deliveries, milestones and some other administrative contraints to build a quality architecture design. By the other hand SOA must be standarize its concepts to avoid misunderstanding between &#8220;Architects&#8221; , business analyst programmers and developers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Grant Czerepak</title>
		<link>http://itknowledgeexchange.techtarget.com/eye-on-oracle/soa-in-09-dead-alive-or-in-search-of-new-meaning/#comment-1384</link>
		<dc:creator>Grant Czerepak</dc:creator>
		<pubDate>Thu, 22 Jan 2009 19:21:10 +0000</pubDate>
		<guid isPermaLink="false">http://eyeonoracle.blogs.techtarget.com/2009/01/19/soa-in-09-dead-alive-or-in-search-of-new-meaning/#comment-1384</guid>
		<description><![CDATA[Any architecture centered on any single aspect of business is destined to fail.  SOA is just another example of this.  I was never in support of SOA.  I never saw Service centrism as a solution.  Data centrism was equally bound to fail.  Event centrism was bound to fail.  All aspects of a system need to be addressed: Goals, Actors, Events, Locations, Services, Products, Units, Measures, Currency, Amounts.  Until we develop an architecture that addresses this correctly, instead of seeking a panacea in centrism, we are destined to architect white elephants.]]></description>
		<content:encoded><![CDATA[<p>Any architecture centered on any single aspect of business is destined to fail.  SOA is just another example of this.  I was never in support of SOA.  I never saw Service centrism as a solution.  Data centrism was equally bound to fail.  Event centrism was bound to fail.  All aspects of a system need to be addressed: Goals, Actors, Events, Locations, Services, Products, Units, Measures, Currency, Amounts.  Until we develop an architecture that addresses this correctly, instead of seeking a panacea in centrism, we are destined to architect white elephants.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
