Blog
How PlanetScale uses database branching and non-blocking schema changes to build PlanetScale. →
The relational model is one of the oldest surviving models in computer science but it has some drawbacks that need to be addressed. →
What database isolation levels actually mean (serializable, snapshot isolation, read committed) and how to choose the right one for distributed and sharded databases. →
We look at some basics and follow up to present scenarios that require higher level intervention to ensure availability and to avoid split brains from taking place. →
Consensus Use Cases →
How the new integration adds new failure detection and recovery scenarios making orchestrator’s operation goal-oriented. →
The Rules of Consensus →
This is a multi-part blog series and will be updated with links to the corresponding posts. →
Learn Horizontal Scaling on PlanetScaleDB with Vitess — Rate Puppies in a Rust app with Sharded MySQL Database
[Engineering, Vitess, MySQL]Rate Puppies in a Rust app with Sharded MySQL Database →
Here at PlanetScale we hear some concerns about the reliability of Vitess and its capabilities with regards to data loss. →
Build systems that do not lose data. Vitess prevents asynchronous failure in two ways: (1) ensuring that the changes are saved locally on storage with the redo log and binary logs safely written to disk and (2) making use of semi-synchronous replication. →
It’s easier than ever to contribute to Vitess. The test suite migration from Python to golang makes Vitess more developer friendly. →