Blog
Get the RSS feedLearn how PlanetScale Metal was built and how we ensured it is safe. →
Learn how PlanetScale keeps its private fork of Vitess up-to-date with OSS →
Learn about the database sharding scaling pattern in this interactive blog. →
Design considerations for implementing a database throttler →
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. →
You can now use the vector data type for vector search and storage in your PlanetScale MySQL database. →
Design considerations for implementing a database throttler with a comparison of singular vs distributed throttler deployments. →
B-trees are used by many modern DBMSs. Learn how they work, how databases use them, and how your choice of primary key can affect index performance. →
PlanetScale now supports instant DDL. Where eligible, you can run deploy requests that complete near-instantly. →
Learn about some design considerations for implementing a database throttler. →
For big databases, IOPS and throughput can become a bottleneck in database performance. Learn how sharding helps scale out IOPS and throughput beyond the limitations of a single server. →
Learn about the new PlanetScale Insights index tracking feature. →
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. →
Sharding a database comes with many benefits: Scalability, failure isolation, write throughput, and more. However, one of the lesser-known benefits comes from improved backups and restore performance. →
Learn the basics of Change Data Capture (CDC) and how to leverage Vitess VStream API to build data pipelines. →
Learn about the options for running non-blocking schema changes natively to MySQL, using Vitess, or other tools →
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. →
Large databases often have a small number of very large tables that makes scaling difficult. How can you scale with these while keeping your database performant? This article covers three techniques. →
Learn about the different types of sharding: directory-based, range-based, and hash-based plus some of the pros and cons of each. →
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 →
The adaptive hash index helps to improve performance of the already-fast B-tree lookups →