Blog
Get the RSS feedLearn 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 →
Matt Robenolt, Iheanyi Ekechukwu |
With global replica credentials, you can now automatically route reads to the closest replica. →
Learn how to visualize the memory usage of a MySQL connection →
My experience working as an intern in the Vitess query serving team for PlanetScale. →
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. →
Vitess 19 is now generally available. →
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. →
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. →
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. →
You can now build integrations that seamlessly authenticate with PlanetScale and allow management access to your users’ organizations and databases from your application. →
Nick Van Wiggeren [@NickVanWig] |
Today, in our effort to continue being the best database for serverless and applications that require massive scale, we are deprecating the Scaler plan. →
Learn the key differences between Amazon Aurora blue/green deployments and PlanetScale branching. →
Learn about the three main aspects of database scaling: storage, compute, and network. →