<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://www.itworld.com" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>SOA pattern</title>
 <link>http://www.itworld.com/taxonomy/term/4469/all</link>
 <description></description>
 <language>xx</language>
<item>
 <title>SOA Pattern (#8): ESB Pattern</title>
 <link>http://www.itworld.com/soa/77213/soa-pattern-8-esb-pattern</link>
 <description>The ESB is a compound pattern that pulls together many enablement and enforcement capabilities that come in handy to the SOA practitioner. Thomas Rischbeck explains it here.
</description>
 <comments>http://www.itworld.com/soa/77213/soa-pattern-8-esb-pattern#comments</comments>
 <category domain="http://www.itworld.com/service-oriented-architecture">SOA</category>
 <category domain="http://www.itworld.com/tip">Tip</category>
 <category domain="http://www.itworld.com/esb">ESB</category>
 <category domain="http://www.itworld.com/soa-pattern">SOA pattern</category>
 <pubDate>Thu, 10 Sep 2009 10:48:41 -0400</pubDate>
 <dc:creator>ITworld staff</dc:creator>
 <guid isPermaLink="false">77213 at http://www.itworld.com</guid>
</item>
<item>
 <title>SOA Pattern of the Week (#7): Policy Centralization</title>
 <link>http://www.itworld.com/soa/69525/soa-pattern-week-7-policy-centralization</link>
 <description>The Policy Centralization pattern advocates that we keep a reusable policy in a single definition and have service contracts to which the policy applies, link to and share this definition.
</description>
 <comments>http://www.itworld.com/soa/69525/soa-pattern-week-7-policy-centralization#comments</comments>
 <category domain="http://www.itworld.com/service-oriented-architecture">SOA</category>
 <category domain="http://www.itworld.com/tip">Tip</category>
 <category domain="http://www.itworld.com/soa-pattern">SOA pattern</category>
 <pubDate>Fri, 19 Jun 2009 11:47:53 -0400</pubDate>
 <dc:creator>ITworld staff</dc:creator>
 <guid isPermaLink="false">69525 at http://www.itworld.com</guid>
</item>
<item>
 <title>SOA Pattern of the Week (#6): Canonical Schema</title>
 <link>http://www.itworld.com/soa/68155/soa-pattern-week-6-canonical-schema</link>
 <description>Of all the patterns in the SOA design patterns catalog there is perhaps no other as simple to understand yet as difficult to apply in practice as Canonical Schema. There are also few patterns that spark as much debate. 
</description>
 <comments>http://www.itworld.com/soa/68155/soa-pattern-week-6-canonical-schema#comments</comments>
 <category domain="http://www.itworld.com/service-oriented-architecture">SOA</category>
 <category domain="http://www.itworld.com/feature">Feature</category>
 <category domain="http://www.itworld.com/soa-pattern">SOA pattern</category>
 <pubDate>Tue, 19 May 2009 16:26:39 -0400</pubDate>
 <dc:creator>ITworld staff</dc:creator>
 <guid isPermaLink="false">68155 at http://www.itworld.com</guid>
</item>
<item>
 <title>SOA Pattern of the Week (#5): Service Decomposition</title>
 <link>http://www.itworld.com/soa/65996/soa-pattern-week-5-service-decomposition</link>
 <description>A service inventory is a living body of services that individually will need the freedom to evolve independently over time. What we learned when documenting the SOA design pattern catalog is that there are patterns that emerged not only at design-time but also during this post-implementation evolutionary stage in a service&#039;s lifecycle.
</description>
 <comments>http://www.itworld.com/soa/65996/soa-pattern-week-5-service-decomposition#comments</comments>
 <category domain="http://www.itworld.com/service-oriented-architecture">SOA</category>
 <category domain="http://www.itworld.com/feature">Feature</category>
 <category domain="http://www.itworld.com/soa-pattern">SOA pattern</category>
 <pubDate>Tue, 07 Apr 2009 13:38:29 -0400</pubDate>
 <dc:creator>ITworld staff</dc:creator>
 <guid isPermaLink="false">65996 at http://www.itworld.com</guid>
</item>
<item>
 <title>SOA Pattern of the Week (#4): Service Normalization</title>
 <link>http://www.itworld.com/soa/63267/soa-pattern-week-4-service-normalization</link>
 <description>Service Normalization is one of many patterns that support service reusability, but its goals go beyond that. Like data normalization, the Service Normalization pattern is intent on reducing redundancy and waste in order to avoid the governance burden associated with having to maintain and synchronize similar or duplicate bodies of service logic.
</description>
 <comments>http://www.itworld.com/soa/63267/soa-pattern-week-4-service-normalization#comments</comments>
 <category domain="http://www.itworld.com/service-oriented-architecture">SOA</category>
 <category domain="http://www.itworld.com/feature">Feature</category>
 <category domain="http://www.itworld.com/soa-pattern">SOA pattern</category>
 <pubDate>Wed, 25 Feb 2009 15:45:03 -0500</pubDate>
 <dc:creator>ITworld staff</dc:creator>
 <guid isPermaLink="false">63267 at http://www.itworld.com</guid>
</item>
<item>
 <title>SOA Pattern of the Week (#3): Domain Inventory</title>
 <link>http://www.itworld.com/soa/62143/soa-pattern-week-3-domain-inventory</link>
 <description>Enterprise-wide harmonization is a desirable and ideal target state that fully supports pretty much everything SOA and service-orientation stand for. For those that have achieved such a state, bless your standardized hearts. You have accomplished something that has eluded many others. However, not attaining this state does not mean you cannot successfully adopt SOA.
</description>
 <comments>http://www.itworld.com/soa/62143/soa-pattern-week-3-domain-inventory#comments</comments>
 <category domain="http://www.itworld.com/service-oriented-architecture">SOA</category>
 <category domain="http://www.itworld.com/feature">Feature</category>
 <category domain="http://www.itworld.com/soa-pattern">SOA pattern</category>
 <pubDate>Thu, 05 Feb 2009 16:30:00 -0500</pubDate>
 <dc:creator>ITworld staff</dc:creator>
 <guid isPermaLink="false">62143 at http://www.itworld.com</guid>
</item>
</channel>
</rss>
