Neki, sharded Postgres, is now available. Learn more
Navigation

Blog

Get the RSS feed

Shlomi Noach

Learn about some design considerations for implementing a database throttler. →


Ben Dicken [@BenjDicken]

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. →


Rafer Hazen

Learn about the new PlanetScale Insights index tracking feature. →


Matt Lord

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. →


Ben Dicken [@BenjDicken]

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. →


Matt Lord

Learn the basics of Change Data Capture (CDC) and how to leverage Vitess VStream API to build data pipelines. →


Shlomi Noach

Learn about the options for running non-blocking schema changes natively to MySQL, using Vitess, or other tools →


Andres Taylor

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. →


Ben Dicken [@BenjDicken]

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. →


Holly Guevara [@hollylawly]

Learn about the different types of sharding: directory-based, range-based, and hash-based plus some of the pros and cons of each. →


Vitess Engineering Team

Vitess 20 is now generally available. →


Holly Guevara [@hollylawly]

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 →


Ben Dicken [@BenjDicken]

The adaptive hash index helps to improve performance of the already-fast B-tree lookups →


Matt Robenolt, Iheanyi Ekechukwu

With global replica credentials, you can now automatically route reads to the closest replica. →


Ben Dicken [@BenjDicken]

Learn how to visualize the memory usage of a MySQL connection →


Arvind Murty

My experience working as an intern in the Vitess query serving team for PlanetScale. →


Mike Coutermarsh

Learn how PlanetScale uses GitHub Actions and PlanetScale to automate schema changes on our own application. →


Ben Dicken [@BenjDicken]

MySQL has built-in functionality for collecting statistics on and profiling your MySQL queries. Learn how to leverage these features to identify problems. →


Brian Morrison II

Understand the different versions of UUIDs and why using them as a primary key in MySQL can hurt database performance. →


Vitess Engineering Team

Vitess 19 is now generally available. →


Sam Lambert [@samlambert]

PlanetScale is committed to providing a reliable and sustainable platform for our customers, not just in the short-term, but forever. For this reason, we are prioritizing profitability. →


Taylor Barnett, Rafer Hazen

Automatically receive recommendations to improve database performance, reduce memory and storage, and improve your schema based on production database traffic. →


Taylor Barnett, Rick Branson

You can now enable foreign key constraints to enforce referential integrity in your PlanetScale database. →


Brian Morrison II

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. →