Scaling Your Database Up and Out

A Guide to Distributed DB

An artless introduction to distributed SQL database ย 

SQL isn't Dead ๐Ÿ’€, It's Just Getting Distributed!

(subtitle - "Hey you duped us")
Elephant in the room- PostgreSQL

Let's look into few common issues

What's the solution?

But why to scale? ๐Ÿค”

  • Increase application performance.
    ย 

  • Business needs.

  • Ability to expand the capacity of system resources in order to support the changing usage of your application.
  • This can refer both to increasing and decreasing usage of the application.

How do I scale?

Horizontal Scaling

  • Replication

  • Sharding/Partitioning

agenda.sql

Abhishek
Mishra

๐Ÿฅ‘ Developer Advocate @Yugabyte

๐Ÿ Pythonista

๐Ÿ‘จโ€๐Ÿ‘ฉโ€๐Ÿ‘งโ€๐Ÿ‘ฆ Community first person ๐Ÿ’›

connect with me:

๐Ÿ‘จโ€๐Ÿ’ป "!10x Engineer"

Jabba checkpoint

A distributed database is a database in which data is stored across different physical location.

What is Distributed DB?

ย 

Distributed SQL is a single logical relational database deployed on a cluster of servers' with automatic replication across multiple servers.

What is Distributed SQL?

Distributed SQL DB Architecture

Distributed SQL DB has

  • A SQL API for accessing and manipulating data and objects.
  • Automatic distribution of data across nodes in a cluster.
  • Automatic replication of data in a strongly consistent manner.
  • Support for distributed query execution so clients do not need to know about the underlying distribution of data.
  • Support for distributed ACID transactions.

Examples:

  • Google Cloud Spanner

  • YugabyteDB

  • Cassandra

  • MongoDB

Jabba checkpoint

Cloud Spanner

Cloud Spanner

  • Relational database, built for scale.

  • High availability.

  • Automatic database sharding.

*magic of distributed SQL*

*magic of distributed SQL*

Talk is cheap, show me the demo!

distributed databases

By Abhishek Mishra