<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Interview with Rick Cattell: There is no &#8220;one size fits all&#8221; solution.</title>
	<atom:link href="http://www.odbms.org/blog/2011/01/interview-with-rick-cattell/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.odbms.org/blog/2011/01/interview-with-rick-cattell/</link>
	<description>Trends and Information on Big Data, New Data Management Technologies, and Innovation.</description>
	<lastBuildDate>Wed, 17 Apr 2013 21:47:18 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.1</generator>
	<item>
		<title>By: Barry Morris</title>
		<link>http://www.odbms.org/blog/2011/01/interview-with-rick-cattell/comment-page-1/#comment-6914</link>
		<dc:creator>Barry Morris</dc:creator>
		<pubDate>Tue, 18 Jan 2011 19:19:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.odbms.org/blog/?p=488#comment-6914</guid>
		<description>&quot;In a nutshell, NoSQL datastores give up SQL and they give up ACID transactions, in exchange for scalability.&quot;

It&#039;s not necessary to give up SQL and ACID transactions.  What is needed is a new internal architecture.

NimbusDB (www.nimbusdb.com) retains SQL and ACID whilst scaling-out on commodity machines.

Barry Morris
CEO, NimbusDB Inc.</description>
		<content:encoded><![CDATA[<p>&#8220;In a nutshell, NoSQL datastores give up SQL and they give up ACID transactions, in exchange for scalability.&#8221;</p>
<p>It&#8217;s not necessary to give up SQL and ACID transactions.  What is needed is a new internal architecture.</p>
<p>NimbusDB (www.nimbusdb.com) retains SQL and ACID whilst scaling-out on commodity machines.</p>
<p>Barry Morris<br />
CEO, NimbusDB Inc.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
