<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel rdf:about="http://blogmarks.net/api/marks/tag/message queuing">
<title>Public marks with tag &quot;message queuing&quot;</title>
<description>Public marks with tag &quot;message queuing&quot;</description>
<link>http://blogmarks.net/marks/tag/message queuing</link>
<items><rdf:Seq><rdf:li resource="http://blogmarks.net/api/user/kasi77/mark/727959"/>
</rdf:Seq></items>
</channel>
<item rdf:about="http://blogmarks.net/api/user/kasi77/mark/727959">
<title>Nodalities</title>
<link>http://blogs.talis.com/nodalities/2006/07/let_the_loose_coupling_take_pl.php</link>
<description>The SOA Operating Platform is starting to emerge.  Get your CPU cycles from a supplier like Sun, get your network attached storage and queuing infrastructure from someone like Amazon, get your mapping application services from someone like Google, get your payment services from someone like PayPal, get your Library Domain specific Web Services from someone like Talis.  Who, other than the core utility processing, storage, and queuing service providers,  needs to invest in infrastructure anymore?</description>
<dc:date>2006-07-25T13:05:40Z</dc:date>
<dc:author>kasi77</dc:author>
<dc:subject>message queuing, amazon, soa, library, web</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://blogs.talis.com/nodalities/2006/07/let_the_loose_coupling_take_pl.php"><img border="0" src="http://blogmarks.net/screenshots/2006/08/02/7e1e6ef94bfd3b6a852ae4f295b49656.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://blogs.talis.com/nodalities/2006/07/let_the_loose_coupling_take_pl.php">Nodalities</a></h4>
 
by <a href="http://blogmarks.net/user/kasi77">kasi77</a> 
<p class="description">The SOA Operating Platform is starting to emerge.  Get your CPU cycles from a supplier like Sun, get your network attached storage and queuing infrastructure from someone like Amazon, get your mapping application services from someone like Google, get your payment services from someone like PayPal, get your Library Domain specific Web Services from someone like Talis.  Who, other than the core utility processing, storage, and queuing service providers,  needs to invest in infrastructure anymore?</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/message%2Bqueuing">message queuing</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/amazon">amazon</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/soa">soa</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/library">library</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/web">web</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=727959">Copy</a> | 
<a href="http://blogmarks.net/link/993929">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> </rdf:RDF>