{{announcement.body}}
{{announcement.title}}
Refcard #335

Distributed SQL Essentials

Distributed SQL databases combine the resilience and scalability of a NoSQL database with the full functionality of a relational database. In this Refcard, we explore the essentials to building a distributed SQL architecture, including key concepts, techniques, and operational metrics.

Published: Sep. 11, 2020
1,027
Free PDF for easy Reference

Brought to you by

Yugabyte
refcard cover

Written by

author avatar Andrew Oliver Sr. Director of Product Marketing, Yugabyte
asset cover
Refcard #335

Distributed SQL Essentials

Distributed SQL databases combine the resilience and scalability of a NoSQL database with the full functionality of a relational database. In this Refcard, we explore the essentials to building a distributed SQL architecture, including key concepts, techniques, and operational metrics.

Published: Sep. 11, 2020
1,027
Free PDF for easy Reference

Written by

author avatar Andrew Oliver Sr. Director of Product Marketing, Yugabyte

Brought to you by

Yugabyte
Table of Contents

What Is Distributed SQL?

Fundamentals of Distributed SQL Architecture

Key Operational Metrics

Conclusion

Section 1

What Is Distributed SQL?

Distributed SQL databases are becoming popular with organizations interested in moving data infrastructure to the cloud and/or cloud-native environments in order to reduce TCO, move away from the horizontal scaling limitations of monolithic RDBMSs like Oracle, PostgreSQL, MySQL, and SQL Server. The basic characteristics of distributed SQL are: 

  • A SQL API for querying and modeling data, with support for traditional RDBMS features like foreign keys, partial indexes, stored procedures, and triggers. 
  • An automatic distributed query execution so that no single node becomes a bottleneck. 
  • Automatic and transparent distributed data storage including indexes, sharded across multiple nodes of the cluster so that no single node becomes a bottleneck. Data distribution ensures high performance and high availability. 
  • Strongly consistent replication and distributed ACID transactions.

This is a preview of the Distributed SQL Essentials Refcard. To read the entire Refcard, please download the PDF from the link above.

Section 2

Fundamentals of Distributed SQL Architecture

Using or migrating to a distributed SQL database requires considering your workload, application architecture, performance, consistency requirements, geographic topography, and execution environment. Match application requirements to the capabilities and configuration of a distributed SQL database to ensure your business and customer needs are met. 

In this section, we explore key concepts of a distributed SQL architecture:

  • Consider your workload
  • Select the appropriate application architecture
  • Make and meet performance requirements
  • Understand consistency
  • Geographic locality
  • Execution environment — to K8s or not to K8s

This is a preview of the Distributed SQL Essentials Refcard. To read the entire Refcard, please download the PDF from the link above.

Section 3

Key Operational Metrics

When operating your distributed SQL database, some key metrics should be monitored. These metrics help determine whether your system is healthy and your business requirements are being met. 

This section highlights key operational metrics for implementing a successful distributed SQL database:

  • Operations per second
  • Average latency
  • Disk usage
  • CPU usage
  • Cost
  • Query plans

This is a preview of the Distributed SQL Essentials Refcard. To read the entire Refcard, please download the PDF from the link above.

Section 4

Conclusion

Distributed SQL databases are critical infrastructure for taking systems of record to the cloud or operating them at Internet scale. These systems match the scale and resilience of a NoSQL database with the full-featured performance of a relational database. Whether the consideration is for an existing workload or a new system of record, any application that requires scale, low latency, transactional integrity, or general resilience is a good candidate for a distributed SQL database. 


This is a preview of the Distributed SQL Essentials Refcard. To read the entire Refcard, please download the PDF from the link above.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}