<?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>Cockroachdb on Karpoke - Just Another Blog</title><link>http://karpoke.ignaciocano.com/tags/cockroachdb/</link><description>Recent content in Cockroachdb on Karpoke - Just Another Blog</description><generator>Hugo -- 0.167.0</generator><language>es</language><lastBuildDate>Sun, 02 Oct 2016 14:42:00 +0100</lastBuildDate><atom:link href="http://karpoke.ignaciocano.com/tags/cockroachdb/index.xml" rel="self" type="application/rss+xml"/><item><title>The design of CockroachDB</title><link>http://karpoke.ignaciocano.com/2016/10/02/the-design-of-cockroachdb/</link><pubDate>Sun, 02 Oct 2016 14:42:00 +0100</pubDate><guid>http://karpoke.ignaciocano.com/2016/10/02/the-design-of-cockroachdb/</guid><description>&lt;blockquote&gt;
&lt;p&gt;CockroachDB is a distributed SQL database. The primary design goals are
scalability, strong consistency and survivability (hence the name).
CockroachDB aims to tolerate disk, machine, rack, and even datacenter
failures with minimal latency disruption and no manual intervention.
CockroachDB nodes are symmetric; a design goal is homogeneous deployment
(one binary) with minimal configuration and no required external
dependencies.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;» Spencer Kimball | &lt;a href="https://github.com/cockroachdb/cockroach/blob/develop/docs/design.md"&gt;github.com&lt;/a&gt;&lt;/p&gt;</description></item></channel></rss>