<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://arnonrotem-gal-oz.sys-con.com"  xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>Latest News from Arnon Rotem-Gal-Oz</title>
 <link>http://arnonrotem-gal-oz.sys-con.com/</link>
 <description>Latest News from Arnon Rotem-Gal-Oz</description>
 <language>en</language>
 <copyright>Copyright 2009 Ulitzer.com</copyright>
 <generator>Ulitzer.com</generator>
 <lastBuildDate>Sun, 29 Nov 2009 11:33:33 EST</lastBuildDate>
 <docs>http://backend.userland.com/rss</docs>
 <ttl>360</ttl>
<item>
 <title>SOA Patterns: Basic Structural Patterns – Part 3</title>
 <link>http://arnonrotem-gal-oz.sys-con.com/node/714224</link>
 <description>For one of the projects I worked on, we had to build a sales support system for a mobile operator. It would probably not come as a surprise to you if I told you that the competition between mobile operators is very fierce. The result of this competition is that the operator&#039;s marketing departments burn the midnight oil trying to come up with new usage plans and bundles to increase their sales.&lt;p&gt;&lt;a href=&quot;http://arnonrotem-gal-oz.sys-con.com/node/714224&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Sat, 18 Oct 2008 10:14:00 EDT</pubDate>
 <guid isPermaLink="true">http://arnonrotem-gal-oz.sys-con.com/node/714224</guid>
 <comments>http://arnonrotem-gal-oz.sys-con.com/node/714224#feedback</comments>
</item>
<item>
 <title>SOA Patterns: Basic Structural Patterns – Part 2</title>
 <link>http://arnonrotem-gal-oz.sys-con.com/node/714167</link>
 <description>Another important attribute of service construction is: How do we handle messages once we get them either on the edge component or in the service? The Transactional Service Pattern allows for solving this problem while also dealing with reliability problems. The nominal scenario of SOA is for a service to get a request to do something from a service consumer, the service then handles the request, maybe asking other services to do some stuff as well, and then produces one or more reactions for the consumer that initiated the request.&lt;p&gt;&lt;a href=&quot;http://arnonrotem-gal-oz.sys-con.com/node/714167&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Fri, 17 Oct 2008 21:15:00 EDT</pubDate>
 <guid isPermaLink="true">http://arnonrotem-gal-oz.sys-con.com/node/714167</guid>
 <comments>http://arnonrotem-gal-oz.sys-con.com/node/714167#feedback</comments>
</item>
<item>
 <title>SOA Patterns: Basic Structural Patterns - Part 1</title>
 <link>http://arnonrotem-gal-oz.sys-con.com/node/696534</link>
 <description>Service-oriented architecture has become the leading solution for complex, connected business systems. While it&#039;s easy to grasp the theory of SOA, implementing well-designed, practical SOA systems can be a difficult challenge. SOA Patterns provides detailed, technology-neutral solutions to the challenges by providing architectural guidance through patterns and anti-patterns. Part 1 of this excerpt focuses on two patterns that address matters of services. These are the patterns you are most likely to use even if your service has modest requirements.&lt;p&gt;&lt;a href=&quot;http://arnonrotem-gal-oz.sys-con.com/node/696534&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Thu, 02 Oct 2008 17:00:00 EDT</pubDate>
 <guid isPermaLink="true">http://arnonrotem-gal-oz.sys-con.com/node/696534</guid>
 <comments>http://arnonrotem-gal-oz.sys-con.com/node/696534#feedback</comments>
</item>
</channel>
</rss>
