Blog
Our experience upgrading the Query Insights database to PlanetScale Metal →
Learn 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 →
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. →
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. →
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 about the options for running non-blocking schema changes natively to MySQL, using Vitess, or other tools →
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. →
The adaptive hash index helps to improve performance of the already-fast B-tree lookups →
Learn how to visualize the memory usage of a MySQL connection →
Learn how PlanetScale uses GitHub Actions and PlanetScale to automate schema changes on our own application. →
MySQL has built-in functionality for collecting statistics on and profiling your MySQL queries. Learn how to leverage these features to identify problems. →
Understand the different versions of UUIDs and why using them as a primary key in MySQL can hurt database performance. →
Amazon Aurora is pitched as a straightforward and scalable database service on AWS, but there are associated costs that you might not be aware of. →
Learn about a few common mistakes when designing your MySQL database schema. →
Learn the key differences between Amazon Aurora blue/green deployments and PlanetScale branching. →
Learn different considerations and best practices for quickly and efficiently recovering your database when downtime hits. →
In this blog post, we explore how complex data and geographic features can be represented in MySQL. →
Learn about how Amazon Aurora replication works, and how it compares to the traditional MySQL replication strategy used by PlanetScale. →
Learn about the various isolation levels used by MySQL to allow concurrency in your database. →