Blog
In part 6 of the Consensus algorithms series we look at how to handle request completions →
In part 5 of our consensus algorithms series we discuss how we handle race conditions and forward progress requirements. →
In part 4 of the consensus algorithms series we look at how algorithm leaders are established and revoked. →
Holly Guevara [@hollylawly], Shlomi Noach |
Learn how we used VReplication to allow for migration reverts with data retention. →
On behalf of the Vitess maintainers, I am pleased to announce the general availability of Vitess 9. →
On behalf of the Vitess maintainers team, I am pleased to announce the general availability of Vitess 8 for MySQL. →
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. →
On behalf of the Vitess maintainers team, I am pleased to announce the general availability of Vitess 7. Major themes include improved SQL support as we continue to progress towards (almost) full MySQL compatibility. →
Here at PlanetScale we hear some concerns about the reliability of Vitess and its capabilities with regards to data loss. →
I am excited to announce the general availability of Vitess 6, the second release to follow our new accelerated release schedule. →
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. →
This video playlist featuring Vitess co-creator Sugu Sougoumarane is an excellent resource to learn more about the features and capabilities of open source Vitess. →
It’s easier than ever to contribute to Vitess. The test suite migration from Python to golang makes Vitess more developer friendly. →