<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://michaelpoulin.sys-con.com"  xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>Latest News from Michael Poulin</title>
 <link>http://michaelpoulin.sys-con.com/</link>
 <description>Latest News from Michael Poulin</description>
 <language>en</language>
 <copyright>Copyright 2009 Ulitzer.com</copyright>
 <generator>Ulitzer.com</generator>
 <lastBuildDate>Wed, 09 Dec 2009 03:58:39 EST</lastBuildDate>
 <docs>http://backend.userland.com/rss</docs>
 <ttl>360</ttl>
<item>
 <title>Resolving RIA-SOA Conflict</title>
 <link>http://michaelpoulin.sys-con.com/node/730632</link>
 <description>From the first days of Rich Internet Application (RIA) technology, many enthusiasts found an analogy between RIA and service-oriented architecture (SOA). Some of them talked about the benefits of a would-be-wonderful use of SOA in RIA; others saw RIA as a SOA face. Nonetheless, there are experts who see a discrepancy between RIA and SOA concepts.&lt;p&gt;&lt;a href=&quot;http://michaelpoulin.sys-con.com/node/730632&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Wed, 26 Nov 2008 09:00:00 EST</pubDate>
 <guid isPermaLink="true">http://michaelpoulin.sys-con.com/node/730632</guid>
 <comments>http://michaelpoulin.sys-con.com/node/730632#feedback</comments>
</item>
<item>
 <title>Logging for SOA</title>
 <link>http://michaelpoulin.sys-con.com/node/665550</link>
 <description>What could be a problem with logging in SOA in the presence of such wonderful tools like log4j, Java’s logging library and similar? Why might we need something special for SOA and why aren’t existing techniques enough? The answer is simple and complex simultaneously – in SOA we are dealing with distributed and composed entities that cause problems in log maintenance, not in log creation.&lt;p&gt;&lt;a href=&quot;http://michaelpoulin.sys-con.com/node/665550&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Wed, 10 Sep 2008 20:00:00 EDT</pubDate>
 <guid isPermaLink="true">http://michaelpoulin.sys-con.com/node/665550</guid>
 <comments>http://michaelpoulin.sys-con.com/node/665550#feedback</comments>
</item>
<item>
 <title>Service Reuse and Entitlement</title>
 <link>http://michaelpoulin.sys-con.com/node/523434</link>
 <description>At a glance the reuse of a service and entitlement to those service results have nothing in common. But on the second thought, the more a service gets reused the greater the chance of serving users with different access rights to the service results. We&#039;ll discuss two models of reuse and see which one is more suitable for resolving data visibility tasks.&lt;p&gt;&lt;a href=&quot;http://michaelpoulin.sys-con.com/node/523434&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Sun, 23 Mar 2008 16:00:00 EDT</pubDate>
 <guid isPermaLink="true">http://michaelpoulin.sys-con.com/node/523434</guid>
 <comments>http://michaelpoulin.sys-con.com/node/523434#feedback</comments>
</item>
<item>
 <title>Considering the SOA Reference Model</title>
 <link>http://michaelpoulin.sys-con.com/node/318420</link>
 <description>The main drivers for SOA-based architectures are to facilitate the manageable growth of large-scale enterprise systems, to facilitate Internet-scale provisioning and the use of services, and to reduce the cost of organization-to-organization cooperation - SOA RM&lt;p&gt;&lt;a href=&quot;http://michaelpoulin.sys-con.com/node/318420&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Mon, 08 Jan 2007 13:45:00 EST</pubDate>
 <guid isPermaLink="true">http://michaelpoulin.sys-con.com/node/318420</guid>
 <comments>http://michaelpoulin.sys-con.com/node/318420#feedback</comments>
</item>
<item>
 <title>Considering the SOA Reference Model</title>
 <link>http://michaelpoulin.sys-con.com/node/314124</link>
 <description>SOA RM:  &#039;...in SOA, services are the mechanism by which needs and capabilities are brought together&#039;  Recently OASIS voted the SOA Reference Model (SOA RM) into a standard. In spite of its high level of abstraction, this model emphasizes the business orientation of SOA.&lt;p&gt;&lt;a href=&quot;http://michaelpoulin.sys-con.com/node/314124&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Wed, 27 Dec 2006 06:00:00 EST</pubDate>
 <guid isPermaLink="true">http://michaelpoulin.sys-con.com/node/314124</guid>
 <comments>http://michaelpoulin.sys-con.com/node/314124#feedback</comments>
</item>
<item>
 <title>Collecting Financial Market Data with Java 5</title>
 <link>http://michaelpoulin.sys-con.com/node/286908</link>
 <description>In this article I&#039;ll share my experience in using the new features in Java 5 for solving an old industry problem, the problem of collecting constantly published financial data in reliable way. The business case example I&#039;m going to discuss relates to the acquisition of some sort of market data published by a financial data source system like Reuters.&lt;p&gt;&lt;a href=&quot;http://michaelpoulin.sys-con.com/node/286908&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Fri, 03 Nov 2006 14:00:00 EST</pubDate>
 <guid isPermaLink="true">http://michaelpoulin.sys-con.com/node/286908</guid>
 <comments>http://michaelpoulin.sys-con.com/node/286908#feedback</comments>
</item>
<item>
 <title>Service Versioning For SOA</title>
 <link>http://michaelpoulin.sys-con.com/node/250503</link>
 <description>(Found in a blog, &#039;Versioning is as inevitable as security.&#039;) SOA development practice isn&#039;t much different from other software development practices except for design and maintenance. Multiple self-containing and aggregated services that interact with others have their own lifecycle and evolution. The loosely coupling model of SOA services significantly simplifies design but creates additional difficulties in maintenance, especially in the interoperability of different service versions.&lt;p&gt;&lt;a href=&quot;http://michaelpoulin.sys-con.com/node/250503&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Wed, 26 Jul 2006 16:15:00 EDT</pubDate>
 <guid isPermaLink="true">http://michaelpoulin.sys-con.com/node/250503</guid>
 <comments>http://michaelpoulin.sys-con.com/node/250503#feedback</comments>
</item>
<item>
 <title>Does a Web Service Make a Service for SOA?</title>
 <link>http://michaelpoulin.sys-con.com/node/219016</link>
 <description>What could be easier than to take your application, wrap it with a Web Service, announce it or register it in the UDDI and get a SOA Service? Even better - take a data warehouse, cover a SQL executing code with a Web Service and expose it to SOA, isn&#039;t it simple? This article is for those architects and managers who like such &#039;simplicity.&#039; If you believe that a Web Service itself doesn&#039;t convert an application into the SOA Service, you might read the article just out of curiosity.&lt;p&gt;&lt;a href=&quot;http://michaelpoulin.sys-con.com/node/219016&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Sat, 13 May 2006 11:00:00 EDT</pubDate>
 <guid isPermaLink="true">http://michaelpoulin.sys-con.com/node/219016</guid>
 <comments>http://michaelpoulin.sys-con.com/node/219016#feedback</comments>
</item>
<item>
 <title>WebLogic Journal: If a Resource Thread Hangs in the Portal</title>
 <link>http://michaelpoulin.sys-con.com/node/185309</link>
 <description>This article describes a workaround design that allows a Portal to survive if its resource starts hanging request threads. How frequently does your Portal experience user requests hanging in the resource? Not frequently, I hope. However, if this happens and the resource continues hanging user requests, the Portal is exposed to a fatal risk of spending all of the configured concurrent user requests and eventually dies.&lt;p&gt;&lt;a href=&quot;http://michaelpoulin.sys-con.com/node/185309&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Thu, 23 Feb 2006 20:00:00 EST</pubDate>
 <guid isPermaLink="true">http://michaelpoulin.sys-con.com/node/185309</guid>
 <comments>http://michaelpoulin.sys-con.com/node/185309#feedback</comments>
</item>
<item>
 <title>Assured Delivery of Audit Data With SOA and Web Services</title>
 <link>http://michaelpoulin.sys-con.com/node/169336</link>
 <description>This article describes two techniques that may be used for assured delivery of important data, specifically, audit data, in distributed systems. We will review design that leads from assured to guaranteed delivery. This task gets more and more important in light of modern global operation risk regulations and related application risk management.&lt;p&gt;&lt;a href=&quot;http://michaelpoulin.sys-con.com/node/169336&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Fri, 13 Jan 2006 13:15:00 EST</pubDate>
 <guid isPermaLink="true">http://michaelpoulin.sys-con.com/node/169336</guid>
 <comments>http://michaelpoulin.sys-con.com/node/169336#feedback</comments>
</item>
<item>
 <title>Entitlement to Data</title>
 <link>http://michaelpoulin.sys-con.com/node/163285</link>
 <description>The requirements for different user-facing applications frequently say something like: &#039;User has to see/read/be shown only funds/records/itineraries/policies he or she is entitled to.&#039; Permissions in these cases usually depend on multiple factors related to the user profile (job role, locale, etc.), to the protected data (data origin, storage, approval status, etc.), or to both. This represents the fine granular entitlement requirements that are rarely supported by commercial systems.&lt;p&gt;&lt;a href=&quot;http://michaelpoulin.sys-con.com/node/163285&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Sat, 07 Jan 2006 14:00:00 EST</pubDate>
 <guid isPermaLink="true">http://michaelpoulin.sys-con.com/node/163285</guid>
 <comments>http://michaelpoulin.sys-con.com/node/163285#feedback</comments>
</item>
<item>
 <title>How To Deal With Architectural Security?</title>
 <link>http://michaelpoulin.sys-con.com/node/131811</link>
 <description>Application architects have heard about the increased importance of security, but in many cases they really don&#039;t know how to approach this issue. In this article, I&#039;ll share my experience and define a few basic steps and checkpoints for building application architecture with security in mind.&lt;p&gt;&lt;a href=&quot;http://michaelpoulin.sys-con.com/node/131811&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Sat, 15 Oct 2005 10:30:00 EDT</pubDate>
 <guid isPermaLink="true">http://michaelpoulin.sys-con.com/node/131811</guid>
 <comments>http://michaelpoulin.sys-con.com/node/131811#feedback</comments>
</item>
</channel>
</rss>
