Blog
Get the RSS feedBy Benjamin Dicken |
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. →
By Holly Guevara |
Learn about the different types of sharding: directory-based, range-based, and hash-based plus some of the pros and cons of each. →
By Holly Guevara |
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. →
By Harshit Gangal, Deepthi Sigireddi |
How we implemented a consistent lookup Vindex in Vitess to ensure data consistency without using 2PC →
By Benjamin Dicken |
The adaptive hash index helps to improve performance of the already-fast B-tree lookups →
By Matt Robenolt, Iheanyi Ekechukwu |
With global replica credentials, you can now automatically route reads to the closest replica. →
By Arvind Murty |
My experience working as an intern in the Vitess query serving team for PlanetScale. →
By Mike Coutermarsh |
Learn how PlanetScale uses GitHub Actions and PlanetScale to automate schema changes on our own application. →
By Benjamin Dicken |
MySQL has built-in functionality for collecting statistics on and profiling your MySQL queries. Learn how to leverage these features to identify problems. →
By Brian Morrison II |
Understand the different versions of UUIDs and why using them as a primary key in MySQL can hurt database performance. →
By Sam Lambert |
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. →
By Taylor Barnett, Rafer Hazen |
Automatically receive recommendations to improve database performance, reduce memory and storage, and improve your schema based on production database traffic. →
By Taylor Barnett, Rick Branson |
You can now enable foreign key constraints to enforce referential integrity in your PlanetScale database. →
By 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. →
By Brian Morrison II |
Learn about a few common mistakes when designing your MySQL database schema. →
By Taylor Barnett |
You can now build integrations that seamlessly authenticate with PlanetScale and allow management access to your users’ organizations and databases from your application. →
By Nick Van Wiggeren |
Today, in our effort to continue being the best database for serverless and applications that require massive scale, we are deprecating the Scaler plan. →
By Brian Morrison II |
Learn the key differences between Amazon Aurora blue/green deployments and PlanetScale branching. →
By Rick Branson |
Learn about the three main aspects of database scaling: storage, compute, and network. →
By Brian Morrison II |
Learn different considerations and best practices for quickly and efficiently recovering your database when downtime hits. →
By Savannah Longoria |
In this blog post, we explore how complex data and geographic features can be represented in MySQL. →
By Brian Morrison II |
Learn about how Amazon Aurora replication works, and how it compares to the traditional MySQL replication strategy used by PlanetScale. →