Menu
Home
People
Places
Arts
History
Plants & Animals
Science
Life & Culture
Technology
Reference.org
Distributed SQL
open-in-new
<h2 id="history">History</h2> <p><a href="/facts/Google/GT9Sugza">Google</a>'s <a href="/facts/Spanner_(database)/TTFD4yJG">Spanner</a> popularized the modern distributed SQL database concept. Google described the database and its architecture in a 2012 whitepaper called "Spanner: Google's Globally-Distributed Database." The paper described Spanner as having evolved from a <a href="/facts/Big_Table/xlXLKV0t">Big Table</a>-like <a href="/facts/Key_value/buweLY96">key value</a> store into a temporal multi-version database where data is stored in "schematized semi-relational tables."<a class="footnote-ref" id="fnref:1" href="#fn:1"><sup>1</sup></a> </p><p>Spanner uses atomic clocks with the Paxos algorithm to accomplish consensus with regards to state distributed between servers. In 2010, and earlier implementation, <a href="/facts/Clustrix/Uf0LwIJT">ClustrixDB</a> (now <a href="/facts/MariaDB/QWobVFIq">MariaDB</a> Xpand) moved from a hardware appliance to a Paxos-based software database<a class="footnote-ref" id="fnref:2" href="#fn:2"><sup>2</sup></a> and was later acquired by <a href="/facts/MariaDB/QWobVFIq">MariaDB</a><a class="footnote-ref" id="fnref:3" href="#fn:3"><sup>3</sup></a> and added to a <a href="/facts/SaaS/LPyPQ5b7">SaaS</a> cloud offering called <a href="/facts/MariaDB/QWobVFIq">SkySQL</a>.<a class="footnote-ref" id="fnref:4" href="#fn:4"><sup>4</sup></a> In 2015, two Google engineers left the company to create <a href="/facts/Cockroach_Labs/pE4sGXAQ">Cockroach DB</a> which achieves similar results using the Raft algorithm without atomic clocks or custom hardware.<a class="footnote-ref" id="fnref:5" href="#fn:5"><sup>5</sup></a> </p><p>Spanner is primarily used for transactional and time-series use cases. However, Google furthered this research with a follow on paper about Google F1 which it describes as a <a href="/facts/Hybrid_transactional/analytical_processing/DpEv41HU">Hybrid transactional/analytical processing</a> database built on Spanner.<a class="footnote-ref" id="fnref:6" href="#fn:6"><sup>6</sup></a> </p> <h2 id="architecture">Architecture</h2> <p>Distributed SQL databases have the following general characteristics: </p> <ul><li>synchronous replication</li> <li>strong transactional consistency across at least availability zones (i.e. <a href="/facts/ACID/XdHkYzHN">ACID</a> compliance)<a class="footnote-ref" id="fnref:7" href="#fn:7"><sup>7</sup></a></li> <li>relational database front end structure – meaning data represented as tables with rows and columns similar to any other <a href="/facts/RDBMS/pEKGmJLy">RDBMS</a></li> <li>automatically <a href="/facts/Shard_(database_architecture)/YSE3YS0M">sharded</a> data storage</li> <li>underlying key–value storage<a class="footnote-ref" id="fnref:8" href="#fn:8"><sup>8</sup></a><a class="footnote-ref" id="fnref:9" href="#fn:9"><sup>9</sup></a></li> <li>native SQL implementation</li></ul> <p>Following the <a href="/facts/CAP_Theorem/qnxvcbLp">CAP Theorem</a>, distributed SQL databases are "CP" or consistent and partition-tolerant. Algorithmically they sacrifice availability in that a failure of a primary node can make the database unavailable for writes. </p><p>All distributed SQL implementations require some kind of temporal synchronization to guarantee consistency. With the exception of Spanner, most do not use custom hardware to provide atomic clocks. Spanner is able to synchronize writes with temporal guarantees. Implementations without custom hardware require servers to compare clock offsets and potentially retry reads.<a class="footnote-ref" id="fnref:10" href="#fn:10"><sup>10</sup></a> </p> <h2 id="distributed-sql-implementations">Distributed SQL implementations</h2> <table><tbody><tr><th>Vendor</th><th>API</th><th>License model</th></tr><tr><td><a href="/facts/Amazon_Aurora/9Y5Gs369">Amazon Aurora</a></td><td><a href="/facts/PostgreSQL/LHdXuHfl">PostgreSQL</a> & <a href="/facts/MySQL/QEEDNBDP">MySQL</a></td><td>Proprietary</td></tr><tr><td>Citus Data (Microsoft)</td><td><a href="/facts/PostgreSQL/LHdXuHfl">PostgreSQL</a></td><td>Open Source (AGPLv3)<a class="footnote-ref" id="fnref:11" href="#fn:11"><sup>11</sup></a></td></tr><tr><td><a href="/facts/CockroachDB/pE4sGXAQ">CockroachDB</a></td><td><a href="/facts/PostgreSQL/LHdXuHfl">PostgreSQL</a>-like</td><td>Proprietary</td></tr><tr><td><a href="/facts/Spanner_(database)/TTFD4yJG">Google Spanner</a></td><td>Proprietary SQL-like</td><td>Proprietary</td></tr><tr><td><a href="/facts/MySQL_Cluster/BwXDHev6">MySQL Cluster</a></td><td><a href="/facts/MySQL/QEEDNBDP">MySQL</a></td><td>Open Source (GPLv2)</td></tr><tr><td><a href="/facts/NuoDB/A5Eaa3Wo">NuoDB</a></td><td>Proprietary SQL</td><td>Proprietary</td></tr><tr><td><a href="/facts/YugabyteDB/oycYMHCN">YugabyteDB</a></td><td><a href="/facts/PostgreSQL/LHdXuHfl">PostgreSQL</a> & <a href="/facts/Apache_Cassandra/WCJyV4rA">Cassandra</a> CQL-like</td><td>Open Source (Apache 2.0)</td></tr><tr><td><a href="/facts/TiDB/lesmbgpA">TiDB</a></td><td><a href="/facts/MySQL/QEEDNBDP">MySQL</a>-like</td><td>Open Source (Apache 2.0)</td></tr><tr><td><a href="/facts/MariaDB/QWobVFIq">MariaDB XPand</a></td><td><a href="/facts/MariaDB/QWobVFIq">MariaDB</a></td><td>Proprietary</td></tr><tr><td><a href="/facts/Teradata/sarnALYT">Teradata</a></td><td>Proprietary SQL-like</td><td>Proprietary</td></tr><tr><td><a href="/facts/YDB_(database)/gkL15IhU">YDB</a><a class="footnote-ref" id="fnref:12" href="#fn:12"><sup>12</sup></a></td><td>Proprietary SQL-like, <a href="/facts/PostgreSQL/LHdXuHfl">PostgreSQL</a>-like</td><td>Open Source (Apache 2.0)</td></tr></tbody></table> <h2 id="compared-to-newsql">Compared to NewSQL</h2> <p>CockroachDB, YugabyteDB and others have at times referred to themselves as <a href="/facts/NewSQL/6Hvrzn0R">NewSQL</a> databases. Some of the NewSQL databases like Citus and Vitess have fundamentally different architectures, but were cited as examples of NewSQL by Matthew Aslett who coined the term.<a class="footnote-ref" id="fnref:13" href="#fn:13"><sup>13</sup></a> In essence, distributed SQL databases are built from the ground-up and NewSQL databases include replication and sharding technologies added to existing client-server relational databases like <a href="/facts/PostgreSQL/LHdXuHfl">PostgreSQL</a>.<a class="footnote-ref" id="fnref:14" href="#fn:14"><sup>14</sup></a> Some experts define DistributedSQL databases as a more specific subset of NewSQL databases.<a class="footnote-ref" id="fnref:15" href="#fn:15"><sup>15</sup></a> </p> <h2 id="references">References</h2> <ol> <li id="fn:1"><p>https://storage.googleapis.com/pub-tools-public-publication-data/pdf/41344.pdf [bare URL PDF] <a href="https://storage.googleapis.com/pub-tools-public-publication-data/pdf/41344.pdf" target="_blank">https://storage.googleapis.com/pub-tools-public-publication-data/pdf/41344.pdf</a> <a href="#fnref:1" class="footnote-back-ref">↩</a></p></li> <li id="fn:2"><p>Higginbotham, Stacey (May 3, 2010). "Clustrix Builds the Webscale Holy Grail: A Database That Scales". gigaom.com. <a href="https://gigaom.com/2010/05/03/clustrix-builds-the-webscale-holy-grail-a-database-that-scales/,%20https://gigaom.com/2010/05/03/clustrix-builds-the-webscale-holy-grail-a-database-that-scales/" target="_blank">https://gigaom.com/2010/05/03/clustrix-builds-the-webscale-holy-grail-a-database-that-scales/,%20https://gigaom.com/2010/05/03/clustrix-builds-the-webscale-holy-grail-a-database-that-scales/</a> <a href="#fnref:2" class="footnote-back-ref">↩</a></p></li> <li id="fn:3"><p>"MariaDB acquires Clustrix". 20 September 2018. <a href="https://techcrunch.com/2018/09/20/mariadb-acquires-clusterix/" target="_blank">https://techcrunch.com/2018/09/20/mariadb-acquires-clusterix/</a> <a href="#fnref:3" class="footnote-back-ref">↩</a></p></li> <li id="fn:4"><p>Baer (dbInsight), Tony. "For MariaDB, it's time to put the pieces together". ZDNet. <a href="https://www.zdnet.com/article/for-mariadb-its-time-to-put-the-pieces-together/" target="_blank">https://www.zdnet.com/article/for-mariadb-its-time-to-put-the-pieces-together/</a> <a href="#fnref:4" class="footnote-back-ref">↩</a></p></li> <li id="fn:5"><p>Morgan, Timothy Prickett (February 22, 2017). "Google Spanner Inspires CockroachDB To Outrun It". The Next Platform. <a href="https://www.nextplatform.com/2017/02/22/google-spanner-inspires-cockroachdb-outrun/" target="_blank">https://www.nextplatform.com/2017/02/22/google-spanner-inspires-cockroachdb-outrun/</a> <a href="#fnref:5" class="footnote-back-ref">↩</a></p></li> <li id="fn:6"><p>https://storage.googleapis.com/pub-tools-public-publication-data/pdf/41344.pdf [bare URL PDF] <a href="https://storage.googleapis.com/pub-tools-public-publication-data/pdf/41344.pdf" target="_blank">https://storage.googleapis.com/pub-tools-public-publication-data/pdf/41344.pdf</a> <a href="#fnref:6" class="footnote-back-ref">↩</a></p></li> <li id="fn:7"><p>The future of databases: distributed SQL & MariaDB ®, retrieved 2022-12-21 <a href="https://www.youtube.com/watch?v=3igIRQqmYc4" target="_blank">https://www.youtube.com/watch?v=3igIRQqmYc4</a> <a href="#fnref:7" class="footnote-back-ref">↩</a></p></li> <li id="fn:8"><p>"The Architecture of a Distributed SQL Database". 23 September 2020 – via www.youtube.com. <a href="https://www.youtube.com/watch?v=avOgswXxayA" target="_blank">https://www.youtube.com/watch?v=avOgswXxayA</a> <a href="#fnref:8" class="footnote-back-ref">↩</a></p></li> <li id="fn:9"><p>https://storage.googleapis.com/pub-tools-public-publication-data/pdf/41344.pdf [bare URL PDF] <a href="https://storage.googleapis.com/pub-tools-public-publication-data/pdf/41344.pdf" target="_blank">https://storage.googleapis.com/pub-tools-public-publication-data/pdf/41344.pdf</a> <a href="#fnref:9" class="footnote-back-ref">↩</a></p></li> <li id="fn:10"><p>"Living Without Atomic Clocks". Cockroach Labs. April 21, 2020. <a href="https://www.cockroachlabs.com/blog/living-without-atomic-clocks/" target="_blank">https://www.cockroachlabs.com/blog/living-without-atomic-clocks/</a> <a href="#fnref:10" class="footnote-back-ref">↩</a></p></li> <li id="fn:11"><p>"citus/LICENSE at 185ac5e01e8c62757c81cdc1d92cffcf6b55f500 · citusdata/citus". GitHub. Retrieved 2024-09-26. <a href="https://github.com/citusdata/citus/blob/185ac5e01e8c62757c81cdc1d92cffcf6b55f500/LICENSE" target="_blank">https://github.com/citusdata/citus/blob/185ac5e01e8c62757c81cdc1d92cffcf6b55f500/LICENSE</a> <a href="#fnref:11" class="footnote-back-ref">↩</a></p></li> <li id="fn:12"><p>"YDB is an open-source Distributed SQL Database that combines high availability and scalability with strong consistency and ACID transactions". ydb.tech. <a href="https://ydb.tech" target="_blank">https://ydb.tech</a> <a href="#fnref:12" class="footnote-back-ref">↩</a></p></li> <li id="fn:13"><p>"What we talk about when we talk about NewSQL — Too much information". <a href="https://blogs.451research.com/information_management/2011/04/06/what-we-talk-about-when-we-talk-about-newsql/" target="_blank">https://blogs.451research.com/information_management/2011/04/06/what-we-talk-about-when-we-talk-about-newsql/</a> <a href="#fnref:13" class="footnote-back-ref">↩</a></p></li> <li id="fn:14"><p>"SQL vs. NoSQL Databases: What's the Difference?". www.ibm.com. 12 June 2022. <a href="https://www.ibm.com/cloud/blog/sql-vs-nosql" target="_blank">https://www.ibm.com/cloud/blog/sql-vs-nosql</a> <a href="#fnref:14" class="footnote-back-ref">↩</a></p></li> <li id="fn:15"><p>Prabagaren, Gokul (October 30, 2019). "NewSQL — The Next Evolution in Databases". Medium. <a href="https://medium.com/capital-one-tech/newsql-the-next-evolution-in-databases-19109973ee53" target="_blank">https://medium.com/capital-one-tech/newsql-the-next-evolution-in-databases-19109973ee53</a> <a href="#fnref:15" class="footnote-back-ref">↩</a></p></li> </ol>