<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>NoSQL on UberMongoose</title>
		<link>http://localhost:1313/tags/nosql/</link>
		<description>Recent content in NoSQL on UberMongoose</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Sat, 12 Oct 2013 09:32:22 +0530</lastBuildDate>
		
			<atom:link href="http://localhost:1313/tags/nosql/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Redis vs Azure</title>
				<link>http://localhost:1313/post/redis-vs-azure/</link>
				<pubDate>Sat, 12 Oct 2013 09:32:22 +0530</pubDate>
				<guid>http://localhost:1313/post/redis-vs-azure/</guid>
				<description>&lt;p&gt;&lt;img src=&#34;http://localhost:1313/images/azure-vs-redis.png&#34; alt=&#34;&#34;&gt;&lt;/p&gt;&#xA;&lt;p&gt;Redis and Azure table storage have a lot in common. Both have no schema’s enforced on the objects that they store. Both have limited complex query capabilities and both are touted as being “post SQL” storage. However there is one major difference between the two that tends to dampen comparisons and that is how they deal with concurrency.&lt;/p&gt;&#xA;&lt;p&gt;Redis deals with concurrency by queuing requests and handling them one at a time. This allows for single instance Redis servers to deliver impressive performance and a bunch of nice features like set intersections and unions. On the down side this limits the scalability of a single Redis instance because you are stuck with just 1 thread doing the actual work.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
