Distributed Database Scaling
Discussions center on horizontal scaling of SQL databases using distributed systems like CockroachDB, YugabyteDB, Citus, and Vitess, versus traditional Postgres limitations with sharding, replication, and consistency challenges.
Activity Over Time
Top Contributors
Keywords
Sample Comments
They mention that PlanetScale uses Vitess, so indeed it might be distributed
Unless they are sharded and replicated distributed databases...
Why not distributed databases like CockroachDB?
it’s generally better to avoid the distributed systems problems if you can. Postgres is very flexible and you get very far with it if you use all it has to offer
How does Citus provide horizontal scaling? How does it work?
No longer an issue with things like Spanner, CockroachDB etc
No, most of the scalable SQL databases are shared-nothing.
Google Spanner, CockroachDB etc are in that category.
It depends on your access pattern, if every application is write heavy to the same data set, this won't work. If every application is light on writes and those are mostly local (like for many SaaS companies), this will work fine with the future Litestream that redirect writes to one db and then distributes the data (if you can live with slightly stale data). Also depends on the size of you company. Slack does 300k/s messages, this won't work :-)
This is a completely different story. YugabyteDB is about transparent sharding and shard horizontal scalability. Every table is split into tablets. A tablet can be thought of as a shard but one still thinks of a table as a whole. Each tablet is replicated. Replicas can be placed in different regions, even in different computing environments. Want to run it across clouds or span the cloud and bare metal? Ignoring the cost and minding latency, why not. It’s still logical single database with whole