<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: SOA Commentary</title>
	<atom:link href="http://itstraighttalk.wordpress.com/2008/12/01/soa-commentary/feed/" rel="self" type="application/rss+xml" />
	<link>http://itstraighttalk.wordpress.com/2008/12/01/soa-commentary/</link>
	<description>The business of IT, simplified.</description>
	<lastBuildDate>Thu, 10 Sep 2009 14:19:06 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Darrell Piatt</title>
		<link>http://itstraighttalk.wordpress.com/2008/12/01/soa-commentary/#comment-44</link>
		<dc:creator>Darrell Piatt</dc:creator>
		<pubDate>Sat, 10 Jan 2009 12:24:21 +0000</pubDate>
		<guid isPermaLink="false">http://itstraighttalk.wordpress.com/?p=210#comment-44</guid>
		<description>Hi Eric,

I actually see SOA as a tool for achieving EA.  EA partially involves rationalizing the entire set of business functionality for an enterprise into the smallest amount of code and components without sacrificing too much.  You strive to optimize the app portfolio, determine what is common/reusable and then strive to eliminate the redundancy.

Achieving the goal of common services in a real-time enterprise simply becomes incredibly easier with SOA and the technological advances of the past decade.  There are standards-based ways to define contracts, security and numerous other concerns.  These standards are vendor-neutral.  Architects begin to think in terms of applications and service inventory.  Composite applications can be assembled from the service inventory a lot faster than doing it the old way (it&#039;s still hard work, though).

I&#039;ve been working on an SOA strategy at my present company for about three years now.  While it&#039;s not perfect yet and probably will never be, I see us achieving a lot of success with it.</description>
		<content:encoded><![CDATA[<p>Hi Eric,</p>
<p>I actually see SOA as a tool for achieving EA.  EA partially involves rationalizing the entire set of business functionality for an enterprise into the smallest amount of code and components without sacrificing too much.  You strive to optimize the app portfolio, determine what is common/reusable and then strive to eliminate the redundancy.</p>
<p>Achieving the goal of common services in a real-time enterprise simply becomes incredibly easier with SOA and the technological advances of the past decade.  There are standards-based ways to define contracts, security and numerous other concerns.  These standards are vendor-neutral.  Architects begin to think in terms of applications and service inventory.  Composite applications can be assembled from the service inventory a lot faster than doing it the old way (it&#8217;s still hard work, though).</p>
<p>I&#8217;ve been working on an SOA strategy at my present company for about three years now.  While it&#8217;s not perfect yet and probably will never be, I see us achieving a lot of success with it.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
