πŸ“Ή The future of AI infrastructure: optimize and shard your database with agents.Watch the talk
Navigation

Blog

Get the RSS feed

Rafer Hazen |

Our experience upgrading the Query Insights database to PlanetScale Metal β†’


Richard Crowley |

Learn how PlanetScale Metal was built and how we ensured it is safe. β†’


Sam Lambert [@samlambert] |

Database goes brrrrrrrrrrr. β†’


Manan Gupta |

Learn how PlanetScale keeps its private fork of Vitess up-to-date with OSS β†’


Ben Dicken [@BenjDicken] |

Learn about the database sharding scaling pattern in this interactive blog. β†’


Shlomi Noach |

Design considerations for implementing a database throttler β†’


Ben Dicken [@BenjDicken] |

Run Vitess workflows right from within PlanetScale. Migrate data from unsharded to sharded keyspaces, manage traffic cutover, and easily revert when problems arise. β†’


Vitess Engineering Team |

Vitess 21 is now generally available. β†’


Holly Guevara [@hollylawly] |

You can now use the vector data type for vector search and storage in your PlanetScale MySQL database. β†’


Shlomi Noach |

Design considerations for implementing a database throttler with a comparison of singular vs distributed throttler deployments. β†’


Ben Dicken [@BenjDicken] |

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. β†’


Shlomi Noach |

PlanetScale now supports instant DDL. Where eligible, you can run deploy requests that complete near-instantly. β†’


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 β†’