Share
Distributed SQL Databases Deconstructed
Abstract: SQL is a popular database language for modern applications because of its flexibility in modeling workloads and how widely understood it is by developers. However, most modern applications running in the cloud require fault tolerance, the ability to scale out and geographic data distribution. These attributes are hard to achieve with traditional monolithic SQL databases, creating the need for distributed SQL databases.
Google’s Cloud Spanner is arguably the world's first truly distributed SQL database that now powers everything from Adwords to Gmail. Given its fully decentralized architecture, it delivers higher performance and availability for geo-distributed SQL workloads than even specialized transactional databases such as Amazon Aurora and Google Percolator. Fortunately, there are now a number of open source derivatives of Google Cloud Spanner such as YugaByte DB, CockroachDB, and TiDB.
This talk will focus on exploring the common architectural paradigms that these databases are built on and how to evaluate the claims made between the different systems.
Presented by Amey Banarse, Principal Data Architect at Yugabyte DB
Amey Banarse
Transcript
68 slides
-
1 © 2019 All rights reserved. Distributed SQL Databases Deconstructed
Understanding Amazon Aurora, Google Spanner & the Spanner Derivatives Amey Banarse Principal Data Architect YugaByte DB -
2 © 2019 All rights reserved. Introduction 2  Amey
Banarse Principal Data Architect, YugaByte DB ♦ Pivotal ♦ FINRA University of Pennsylvania @ameybanarse http://about.me/amey -
3 © 2019 All rights reserved. Types of Data Stores
Today’s Focus OLAP OLTP Write once, Read many Few concurrent sessions Long running, ad-hoc queries Large table scans Petabyte-scale data storage Mixed reads & writes Many concurrent sessions Single-digit ms query latency Point reads & short-range scans Terabyte-scale data storage -
4 © 2019 All rights reserved. Today’s Focus Types of
Data Stores Open Source Proprietary OLAP OLTP NoSQL SQL SQL NoSQL Google BigTable Amazon Aurora Google Spanner Google BigQuery -
5 © 2019 All rights reserved. Why Devs SQL? 1.
Query Flexibility – Model data once, change queries as business changes – Balance modeling richness with performance needs 2. Rich Ecosystem – Data modeling & query examples – Developer IDEs & data visualization tools – Easy to reuse & build integrations 3. Universal Standard for Data Access – Learn once, use forever -
6 © 2019 All rights reserved. Why Devs SQL? 1.
Large Dataset? – No horizontal write scalability – Use manually sharded SQL or non-transactional NoSQL 2. Infrastructure Failures? – No native failover & repair, SPOF w/ Single Node DB – Use complex replication schemes 3. Multi-Region/Geo-Distributed App? – Multi-master deployment is the only option – Data inconsistency w/ Last Writer Wins (LWW) conflict resolution -
7 © 2019 All rights reserved. Distributed SQL = Keep
& Remove 1. SQL Features – ACID, JOINs, foreign keys, serializable isolation 2. Horizontal Write Scalability – Scale write throughput by adding/removing nodes 3. Fault Tolerance With High Availability – Native failover & repair 4. Globally Consistent Writes – Lower end user latency and tolerate region failures 5. Low Read Latency – Strongly consistent (aka correct) reads -
8 © 2019 All rights reserved. What’s the fastest growing
service in AWS? -
11 © 2019 All rights reserved. What database powers Google
AdWords and Google Play? -
12 © 2019 All rights reserved. “At Google, Spanner supports
tens of millions of queries per second and runs some of our most critical services, including AdWords and Google Play.” https://ai.google/research/pubs/pub39966 Google Cloud Spanner -
13 © 2019 All rights reserved. Distributed SQL Architectures -
Aurora vs Spanner Amazon Aurora Google Cloud Spanner “A highly available MySQL and PostgreSQL-compatible relational database service” Available on AWS since 2015 “The first horizontally scalable, strongly consistent, relational database service” Available on Google Cloud since 2017 Shared Storage Shared Nothing -
14 © 2019 All rights reserved. #1 SQL Features and
Completeness -
15 © 2019 All rights reserved. Depth of SQL Support
✓ MySQL and PostgreSQL-compatible Subset of MySQL/PostgreSQL features Amazon Aurora Google Cloud Spanner -
16 © 2019 All rights reserved. Aurora vs Spanner Feature
Amazon Aurora Google Spanner SQL Features ✓ Horizontal Write Scalability ✓ Fault Tolerance with HA ✓ Globally Consistent Writes ✓ Low Read Latency -
18 © 2019 All rights reserved. Amazon Aurora Single Node
SQL on Multi-Zone Distributed Storage SQL APP INSERT ROW ❌ Add Primary Instances for Write Scaling ✓ Add Read Replicas for Read Scaling -
19 © 2019 All rights reserved. Google Spanner Multi-Node SQL
on Multi-Region Distributed Storage SQL APP INSERT ROW3 ✓ Add Primary Instances for Write Scaling ✓ Add Read Replicas for Read Scaling INSERT ROW1 -
20 © 2019 All rights reserved. Aurora vs Spanner Feature
Amazon Aurora Google Spanner SQL Features ✓ Horizontal Write Scalability ❌ ✓ Fault Tolerance with HA Globally Consistent Writes Low Read Latency -
22 © 2019 All rights reserved. Amazon Aurora Native Failover
& Repair Through Primary Auto Election SQL APP ✓ HA When Primary Instance Fails ✓ HA When Read Replica Fails INSERT ROW -
23 © 2019 All rights reserved. Google Spanner Native Failover
& Repair Through Shard Leader Auto Election SQL APP INSERT ROW1 ✓ HA When Any Primary Node Fails ✓ HA When Read Replica Fails INSERT ROW3 -
24 © 2019 All rights reserved. Aurora vs Spanner Feature
Amazon Aurora Google Spanner SQL Features ✓ Horizontal Write Scalability ❌ ✓ Fault Tolerance with HA ✓ ✓ Globally Consistent Writes Low Read Latency -
26 © 2019 All rights reserved. Amazon Aurora Multi-Master Last
Writer Wins Conflict Resolution Leads to Inconsistencies SQL APP SET BALANCE = BALANCE - 10 SQL APP SET BALANCE = BALANCE - 100 Asynchronous Replication Region 1 Region 2 -
27 © 2019 All rights reserved. Google Spanner Purpose-Built for
Globally Consistent Writes SQL APP SET BALANCE = BALANCE - 10 SQL APP SET BALANCE = BALANCE - 100 -
28 © 2019 All rights reserved. Aurora vs Spanner Feature
Amazon Aurora Google Spanner SQL Features ✓ Horizontal Write Scalability ❌ ✓ Fault Tolerance with HA ✓ ✓ Globally Consistent Writes ❌ ✓ Low Read Latency -
30 © 2019 All rights reserved. Amazon Aurora Strongly Consistent
Reads Served By Primary Instance SQL APP READ ROW -
31 © 2019 All rights reserved. Google Spanner Strongly Consistent
Reads Served By Shard Leaders w/o Read Quorum SQL APP READ ROW1 -
32 © 2019 All rights reserved. Aurora vs Spanner Feature
Amazon Aurora Google Spanner SQL Features ✓ Horizontal Write Scalability ❌ ✓ Fault Tolerance with HA ✓ ✓ Globally Consistent Writes ❌ ✓ Low Read Latency ✓ ✓ -
33 © 2019 All rights reserved. Battle of Architectures -
Spanner Beats Aurora No Performance & Availability Bottlenecks Scale to Large Clusters while Remaining Highly Available Built for Geo-Distributed Apps Future Proofs Data Tier at Global Businesses Complex to Engineer Needs Clock Skew Tracking Across Instances -
34 © 2019 All rights reserved. Analyzing Open Source Spanner
Inspired Derivatives -
35 © 2019 All rights reserved. Spanner Brought to Life
in Open Source -
36 © 2019 All rights reserved. YugaByte DB Design Principles
• CP in CAP Theorem • Consistent • Partition Tolerant • HA on failures (new leader elected in seconds) • ACID Transactions • Single-row linearizability • Multi-row ACID • Serializable & Snapshot • No bottlenecks even for geo-distributed rows • High Performance • All layers in C++ to ensure high perf • Run on large memory machines • Optimized for SSDs • Deploy Anywhere • No IaaS specific dependencies • No atomic clocks • Bare metal, VM and Kubernetes -
37 © 2019 All rights reserved. Functional Architecture DOCDB Spanner-Inspired
Distributed Document Store CLOUD NEUTRAL No Specialized Hardware Needed YSQL PostgreSQL-Compatible Distributed SQL API tablet 1’ tablet 1’ -
38 © 2019 All rights reserved. Design Follows a Layered
Approach tablet 1’ tablet 1’ tablet 1’ Self-Healing, Fault-Tolerant Auto Sharding & Rebalancing ACID Transactions Global Data Distribution High Throughput, Low Latency YCQL SQL-Based Flexible Schema API YSQL Globally Distributed Postgres API -
40 © 2019 All rights reserved. Distributed SQL = Keep
& Remove 1. SQL Features 2. Replication Protocol 3. Clock Skew Tracking 4. Geo-Distributed Transactions -
41 © 2019 All rights reserved. Spanner vs. its Open
Source Derivatives Feature Google Spanner YugaByte DB CockroachDB TiDB Cost Expensive Free Free Free SQL API Compatibility Replication Protocol Clock Skew Tracking Geo-Distributed Txns Tunable Read Latency Official Jepsen Tests -
44 © 2019 All rights reserved. Depth of SQL Support
- YugaByte DB • SQL Features • Data Types • Relational Integrity (Foreign Keys) • Built-in Functions • Expressions • JSON Column Type • Secondary Indexes • JOINs • Transactions • Views • Advanced SQL Features • Partial Indexes • Stored Procedures • Triggers • And more ... -
45 © 2019 All rights reserved. Spanner vs. its Open
Source Derivatives Feature Google Spanner YugaByte DB CockroachDB TiDB Cost Expensive Free Free Free SQL API Compatibility Proprietary PostgreSQL PostgreSQL No Stored Procedures MySQL No Foreign Keys Replication Protocol Clock Skew Tracking Transaction Manager Tunable Read Latency Official Jepsen Tests -
47 © 2019 All rights reserved. Every Table is Automatically
Sharded tablet 1’ … … … … … … … … … … … … … … … SHARDING = AUTOMATIC PARTITIONING OF TABLES -
48 © 2019 All rights reserved. Replication Done at Shard
Level tablet 1’ Tablet Peer 1 on Node X Tablet #1 Tablet Peer 2 on Node Y Tablet Peer 3 on Node Z -
49 © 2019 All rights reserved. Replication uses a Consensus
algorithm tablet 1’ Raft Leader Uses Raft Algorithm First elect Tablet Leader -
50 © 2019 All rights reserved. Writes in Raft Consensus
tablet 1’ Raft Leader Writes processed by leader: Send writes to all peers Wait for majority to ack Write -
51 © 2019 All rights reserved. Reads in Raft Consensus
tablet 1’ Raft Leader Reads handled by leader Uses Leader Leases for performance Read -
52 © 2019 All rights reserved. Spanner vs. its Open
Source Derivatives Feature Google Spanner YugaByte DB CockroachDB TiDB Cost Expensive Free Free Free SQL API Compatibility Proprietary PostgreSQL PostgreSQL No Stored Procedures MySQL No Foreign Keys Replication Protocol Paxos Raft Raft Raft Clock Skew Tracking Geo-Distributed Txns Tunable Read Latency Official Jepsen Tests -
54 © 2019 All rights reserved. Multi-Shard Transactions tablet 1’
k1 and k2 may belong to different shards BEGIN TXN UPDATE k1 UPDATE k2 COMMIT Belong to different Raft groups on completely different nodes -
55 © 2019 All rights reserved. What do Distributed Transactions
need? tablet 1’ Updates should get written at the same physical time Raft Leader Raft Leader BEGIN TXN UPDATE k1 UPDATE k2 COMMIT But how will nodes agree on time? -
56 © 2019 All rights reserved. Use a Physical Clock
tablet 1’ You would need an Atomic Clock or two lying around Atomic Clocks are highly available, globally synchronized clocks with tight error bounds Most of my physical clocks are never synchronized Jeez! I’m fresh out of those. -
57 © 2019 All rights reserved. Hybrid Logical Clock or
HLC tablet 1’ Combine coarsely-synchronized physical clocks with Lamport Clocks to track causal relationships (physical component, logical component) synchronized using NTP a monotonic counter Nodes update HLC on each Raft exchange for things like heartbeats, leader election and data replication -
58 © 2019 All rights reserved. Spanner vs. its Open
Source Derivatives Feature Google Spanner YugaByte DB CockroachDB TiDB Cost Expensive Free Free Free SQL API Compatibility Proprietary PostgreSQL PostgreSQL No Stored Procedures MySQL No Foreign Keys Replication Protocol Paxos Raft Raft Raft Clock Skew Tracking TrueTime Atomic Clock Hybrid Logical Clock + Max Clock Skew Hybrid Logical Clock + Max Clock Skew Single Timestamp Gen ⇒ No Tracking Needed Geo-Distributed Txns ✓ ✓ ✓ Not Recommended Given Single (Region) Timestamp Generator Tunable Read Latency Official Jepsen Tests -
60 © 2019 All rights reserved. Jepsen.io Testing Jepsen is
an effort to improve the safety of distributed databases, queues, consensus systems, etc. led by Kyle Kingsbury “YugaByte DB now passes tests for snapshot isolation, linearizable counters, sets, registers, and systems of registers, as long as clocks are well-synchronized” Jepsen YugaByteDB Analysis: https://jepsen.io/analyses/yugabyte-db-1.1.9 -
61 © 2019 All rights reserved. Spanner vs. its Open
Source Derivatives Feature Google Spanner YugaByte DB CockroachDB TiDB Cost Expensive Free Free Free SQL API Compatibility Proprietary PostgreSQL PostgreSQL No Stored Procedures MySQL No Foreign Keys Replication Protocol Paxos Raft Raft Raft Clock Skew Tracking TrueTime Atomic Clock Hybrid Logical Clock + Max Clock Skew Hybrid Logical Clock + Max Clock Skew Single Timestamp Gen ⇒ No Tracking Geo-Distributed Txns ✓ ✓ ✓ Not Recommended Given Single (Region) Timestamp Generator Tunable Read Latency ✓ ✓ ❌ ❌ Official Jepsen Tests Unknown ✓ ✓ ✓ -
63 © 2019 All rights reserved. Read more at blog.yugabyte.com
blog.yugabyte.com/distributed-postgresql-on-a-google-spanner-architecture-storage-layer Storage Layer blog.yugabyte.com/distributed-postgresql-on-a-google-spanner-architecture-query-layer Query Layer -
64 © 2019 All rights reserved. Questions? Join Slack Discussions
yugabyte.com/slack Check out on GitHub https://github.com/YugaByte/yugabyte-db docs.yugabyte.com/quick-start -
65 © 2019 All rights reserved. Relevant Research Publications •
Bigtable: http://static.googleusercontent.com/media/research.google.com/en//archive/bigtable-osdi06.pdf • Spanner: ◦ http://static.googleusercontent.com/media/research.google.com/en//archive/spanner-osdi20 12.pdf • Megastore: ◦ http://static.googleusercontent.com/media/research.google.com/en//pubs/archive/36971.pdf • Raft algorithm ◦ http://ramcloud.stanford.edu/raft.pdf ◦ https://raft.gixthub.io/ ◦ http://openlife.cc/system/files/3-modifications-for-Raft-consensus.pdf -
66 © 2019 All rights reserved. Relevant Research Publications •
David Alves, Todd Lipcon, Vijay Garg. Technical Report: HybridTime - Accessible Global Consistency with High Clock Uncertainty. http://pdsl.ece.utexas.edu/david/hybrid-time-tech-report-01.pdf • Sandeep Kulkarni, Murat Demirbas, Deepak Madeppa, Bharadwaj Avva, and Marcelo Leone. Logical Physical Clocks and Consistent Snapshots in Globally Distributed Databases. http://www.cse.buffalo.edu/tech-reports/2014-04.pdf • Michael J. Cahill, Uwe Röhm, Alan D. Fekete. Serializable Isolation for Snapshot Databases (2008). https://courses.cs.washington.edu/courses/cse444/08au/544M/READING-LIST/fekete-sigmod2008.p df • Murat Demirbas, Sandeep Kulkarni. Beyond TrueTime: Using AugmentedTime for Improving Spanner. http://www.cse.buffalo.edu/~demirbas/publications/augmentedTime.pdf • Dahlia Malkhi Jean-Philippe Martin. Spanner’s Concurrency Control. (2) Ittay Eyal. Fault Tolerant Transaction Architectures https://www.cs.cornell.edu/~ie53/publications/DC-col51-Sep13.pdf -
67 © 2019 All rights reserved. Relevant Research Publications •
Coordination Avoidance in Database Systems Peter Bailis, Alan Fekete, Michael J. Franklin, Ali Ghodsi, Joseph M. Hellerstein, Ion Stoica http://www.bailis.org/papers/ca-vldb2015.pdf • RocksDB - RocksDB: A High Performance Embedded Key-Value Store for Flash Storage - Data@Scale , https://www.youtube.com/watch?v=plqVp_OnSzg • Schema-Agnostic Indexing with Azure DocumentDB (VLDB paper): paper describes the Microsoft Azure’s DocumentDB capabilities, including document representation, query language, document indexing approach, core index support, and early production experiences • MergeOperator on RocksDB - https://github.com/facebook/rocksdb/wiki/Merge-Operator-Implementation • Cluster scheduling blog post from cambridge: http://www.cl.cam.ac.uk/research/srg/netos/camsas/blog/2016-03-09-scheduler-architectures.html -
68 © 2019 All rights reserved. Questions? Join Slack Discussions
yugabyte.com/slack Check out on GitHub https://github.com/YugaByte/yugabyte-db docs.yugabyte.com/quick-start