<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Key-Value on Karpoke - Just Another Blog</title><link>http://karpoke.ignaciocano.com/tags/key-value/</link><description>Recent content in Key-Value on Karpoke - Just Another Blog</description><generator>Hugo -- 0.167.0</generator><language>es</language><lastBuildDate>Wed, 08 Jul 2015 21:34:00 +0100</lastBuildDate><atom:link href="http://karpoke.ignaciocano.com/tags/key-value/index.xml" rel="self" type="application/rss+xml"/><item><title>RebornDB: The next generation distributed key-value store</title><link>http://karpoke.ignaciocano.com/2015/07/08/reborndb-the-next-generation-distributed-key-value-store/</link><pubDate>Wed, 08 Jul 2015 21:34:00 +0100</pubDate><guid>http://karpoke.ignaciocano.com/2015/07/08/reborndb-the-next-generation-distributed-key-value-store/</guid><description>&lt;blockquote&gt;
&lt;p&gt;Redis is advanced key-value cache and store, under BSD license. It is
very fast, has many data types(String, Hash, List, Set, Sorted Set …),
uses RDB or AOF persistence and replication to guarantee data
security, and supplies many language client libraries. Most of all,
market chooses Redis. There are many companies using Redis and it has
proved its worth. Although redis is greate, it still has some
disadvantages, and the biggest one is memory limitation. Redis keeps
all data in memory, which limits the whole dataset size and lets us
save more data impossibly.&lt;/p&gt;
&lt;/blockquote&gt;</description></item></channel></rss>