Blog
Increasing throughput sometimes requires reducing parallelism. A look into why this is the case for Vitess + MySQL databases →
Vitess 23 is now generally available →
Vitess 22 is now generally available →
A novel technique for implementing dynamic language interpreters in Go, applied to the Vitess SQL evaluation engine →
Run Vitess workflows right from within PlanetScale. Migrate data from unsharded to sharded keyspaces, manage traffic cutover, and easily revert when problems arise. →
Vitess 21 is now generally available. →
Data migrations are a critical part of the database lifecycle, and are sometimes necessary for version upgrades, sharding, or moving to a new platform. In many cases, migrations are painful and error-prone. In this article, we walk through how migrations are performed at PlanetScale, and offer advice on how to improve the migration experience. →
Learn the basics of Change Data Capture (CDC) and how to leverage Vitess VStream API to build data pipelines. →
The Vitess query planner takes multiple passes over a query plan to optimize it as much as possible before execution. A recent tricky bug report led to an improvement in how the optimizer functions. →
Vitess 20 is now generally available. →
PlanetScale and Vitess have a close relationship. Learn what it looks like to run Vitess on your own vs using PlanetScale. We cover cost, time to implement, management, and more. →
Harshit Gangal, Deepthi Sigireddi |
How we implemented a consistent lookup Vindex in Vitess to ensure data consistency without using 2PC →
My experience working as an intern in the Vitess query serving team for PlanetScale. →
Vitess 19 is now generally available. →
We are releasing schemadiff, an open source command line tool to generate diffs between two MySQL databases. →
Today, PlanetScale launched support for foreign key constraints. This article covers some of the behind-the-scenes technical challenges we had to overcome to support them. →
Vitess 18 is now generally available, with a number of new enhancements designed to improve usability, performance, and MySQL compatibility. →
Not sure when to shard your MySQL or Postgres database? This article covers when you should consider horizontal sharding as a scaling strategy in MySQL and Postgres, and some other scaling options before then. →
Explore what to consider when deploying databases to Kubernetes, and how PlanetScale utilizes Kubernetes and Vitess to run hundreds of thousands of databases. →
Historically, there has been the belief that you cannot horizontally scale and shard MySQL, learn how Vitess has made MySQL sharding at the database layer a reality. →
Learn about all of the tech driving every PlanetScale database. →
Learn how middleware technology works, the pitfalls of application-level sharding, and how Vitess enables horizontal sharding of MySQL for near infinite scale. →
In this release of Vitess, several significant enhancements have been introduced to improve the compatibility, performance, and usability of the system. →
See how Vitess acts as a database proxy that creates an illusion of a single database when technically, the query is sent to multiple MySQL instances. →
Connection pooling reduces the overhead of establishing new database connections. Learn how connection pooling works and how it is handled in Vitess. →