<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://jesusrodriguez.sys-con.com"  xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>Latest News from Jesus Rodriguez</title>
 <link>http://jesusrodriguez.sys-con.com/</link>
 <description>Latest News from Jesus Rodriguez</description>
 <language>en</language>
 <copyright>Copyright 2009 Ulitzer.com</copyright>
 <generator>Ulitzer.com</generator>
 <lastBuildDate>Mon, 07 Dec 2009 11:18:12 EST</lastBuildDate>
 <docs>http://backend.userland.com/rss</docs>
 <ttl>360</ttl>
<item>
 <title>Pragmatic SOA Interoperability</title>
 <link>http://jesusrodriguez.sys-con.com/node/393668</link>
 <description>A well-planned Web Service interoperability environment begins by clearly defining who your Web Service consumers are now and in the future. There was a time not so long ago when you could count on a fairly homogenous consumer population. This was about the same time that you were happy just to be able to get a Web Service running in the first place and finding a consumer who could actually interact with your Web Service was cause for celebration. Those days have changed however and Web Services interoperability, once a &#039;fancy&#039; addition to your SOA design, is now a key and indispensable requirement in most SOA scenarios.&lt;p&gt;&lt;a href=&quot;http://jesusrodriguez.sys-con.com/node/393668&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Tue, 03 Jul 2007 06:30:00 EDT</pubDate>
 <guid isPermaLink="true">http://jesusrodriguez.sys-con.com/node/393668</guid>
 <comments>http://jesusrodriguez.sys-con.com/node/393668#feedback</comments>
</item>
<item>
 <title>Web Services and SOA</title>
 <link>http://jesusrodriguez.sys-con.com/node/291043</link>
 <description>People sometimes ask what a service-oriented architecture enables today that could not have been done with the older, proprietary integration stacks of the past 5 to 15 years, such as those from Tibco, IBM, or Vitria. One such ability is the greater degree of interoperability between heterogeneous technology stacks that is made possible by the standards SOA is built on, such as Web services and BPEL. Although interoperability is only one facet of the SOA value proposition, it is one that has become increasingly more important, due in large part to the evolving IT environment, merger and acquisition activity, and increased partner connectivity.&lt;p&gt;&lt;a href=&quot;http://jesusrodriguez.sys-con.com/node/291043&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Tue, 03 Apr 2007 04:45:00 EDT</pubDate>
 <guid isPermaLink="true">http://jesusrodriguez.sys-con.com/node/291043</guid>
 <comments>http://jesusrodriguez.sys-con.com/node/291043#feedback</comments>
</item>
</channel>
</rss>
