<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>truststix.com Blog &#187; SOA</title>
	<atom:link href="http://truststix.com/blog/index.php/category/soa/feed/" rel="self" type="application/rss+xml" />
	<link>http://truststix.com/blog</link>
	<description>Patterns, Practices and Results</description>
	<lastBuildDate>Sat, 17 May 2008 01:05:47 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Service Oriented Architecture (SOA) Deployment</title>
		<link>http://truststix.com/blog/2008/01/24/service-oriented-architecture-soa-deployment/</link>
		<comments>http://truststix.com/blog/2008/01/24/service-oriented-architecture-soa-deployment/#comments</comments>
		<pubDate>Thu, 24 Jan 2008 00:33:57 +0000</pubDate>
		<dc:creator>Shivaram Mysore</dc:creator>
				<category><![CDATA[SOA]]></category>

		<guid isPermaLink="false">http://www.truststix.com/blog/2008/01/24/service-oriented-architecture-soa-deployment/</guid>
		<description><![CDATA[SOA is all about Architecture.  It is my belief that the Services exposed must also include some form of usage guidance (apart from development API and WSDL).  The usage guidance could be in the form of &#8220;Best Practices for using this Service X&#8221; which should contain some of the scenarios for which this Service was [...]]]></description>
			<content:encoded><![CDATA[<p>SOA is all about Architecture.  It is my belief that the Services exposed must also include some form of usage guidance (apart from development API and WSDL).  The usage guidance could be in the form of &#8220;Best Practices for using this Service X&#8221; which should contain some of the scenarios for which this Service was developed.  It must also contain how this Service can be used in &#8220;Enterpise Integration Patterns&#8221;.  An excellent cheat of these Patterns is available <a title="Enterprise Integration Patterns" href="http://www.enterpriseintegrationpatterns.com/toc.html">here</a>. This guidance is necesary for developing a Threat Model not only for the Service being provided, but also for developing a Threat Model for the another Service or Application that is consuming this published Service.</p>
<p>Microsoft has published excellent information on developing <a title="Threat Modelling" href="http://msdn2.microsoft.com/en-us/security/aa570411.aspx">Threat Models</a>, necessary <a title="Threat Modelling Tool" href="http://www.microsoft.com/downloads/details.aspx?familyid=62830f95-0e61-4f87-88a6-e7c663444ac1&#038;displaylang=en">Tools</a> and <a title="Threat Modelling Blog" href="http://blogs.msdn.com/threatmodeling/">Blog</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://truststix.com/blog/2008/01/24/service-oriented-architecture-soa-deployment/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.486 seconds -->
