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*
-
Start YugabyteDB locally: https://bit.ly/yb-docker
-
Read more about app: https://bit.ly/market-order-app-yb
Talk is cheap, show me the demo!
Join our community - yugabyte.com/slack
-
Star the repo - yugabyte/yugabyte-db
Try for yourself - cloud.yugabyte.com
