<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://jimmurphy.sys-con.com"  xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>Latest News from Jim Murphy</title>
 <link>http://jimmurphy.sys-con.com/</link>
 <description>Latest News from Jim Murphy</description>
 <language>en</language>
 <copyright>Copyright 2009 Ulitzer.com</copyright>
 <generator>Ulitzer.com</generator>
 <lastBuildDate>Sat, 07 Nov 2009 08:30:10 EST</lastBuildDate>
 <docs>http://backend.userland.com/rss</docs>
 <ttl>360</ttl>
<item>
 <title>My Design Time Is Your Runtime</title>
 <link>http://jimmurphy.sys-con.com/node/380233</link>
 <description>You&#039;ve deployed a Web Service. It&#039;s been designed, built, tested, and published to your registry for use and is now a critical component in a strategic business application. Your SOA is beginning to show signs of return but what happens when other architects discover your service and begin to design new applications with it? On one hand, you&#039;re seeing the benefits of reuse, yet how can you manage a service that&#039;s undergoing continuous testing? What happens to your initial business application when one of its key services undergoes a load test for another composite application?&lt;p&gt;&lt;a href=&quot;http://jimmurphy.sys-con.com/node/380233&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Tue, 29 May 2007 17:30:00 EDT</pubDate>
 <guid isPermaLink="true">http://jimmurphy.sys-con.com/node/380233</guid>
 <comments>http://jimmurphy.sys-con.com/node/380233#feedback</comments>
</item>
</channel>
</rss>
