Blog
Get the RSS feedBy Brian Morrison II |
Learn the best practices for configuring MySQL replication, and how to ensure your data is always available. →
By Ayrton |
Learn how to build HTML emails using Rails and Tailwind CSS. We also cover how to overcome some common obstacles such as Gmail message clipping, large file size, Apple autolinking, and more. →
By David Bravant |
Maximizing performance while minimizing costs is integral for engineering large-scale applications with massive data volumes. Learn more about cost-effective sharding in this tech talk. →
By Sam Lambert |
We are pleased to announce that PlanetScale has been named on the Deloitte Technology Fast 500™. →
By Vitess Engineering Team |
Vitess 18 is now generally available, with a number of new enhancements designed to improve usability, performance, and MySQL compatibility. →
By Taylor Barnett, Katie Sipos |
Learn how you can extract, load, and transform your PlanetScale data with Fivetran. →
By Taylor Barnett, Mike Coutermarsh |
You can now automatically trigger HTTP callbacks on events in PlanetScale to build custom integrations, notifications, and workflows. →
By Brian Morrison II |
Learn about what database replication is and some real-world use cases of MySQL replication that can benefit your database scalability strategy. →
By Brian Morrison II |
Learn how to sync user data from a Clerk project into your PlanetScale MySQL database with webhooks using Netlify and Netlify Functions. →
By Frances Thai |
Bringing weekly reports of the most important parts of your database, straight to your inbox. →
By Brian Morrison II |
Learn what distributed caching systems are, how they complement MySQL databases, and potential issues you might face when implementing them. →
By Brian Morrison II |
Learn the basics of MySQL partitioning, including partitioning with range, list, and key strategies, as well as how partitioning relates to database sharding. →
By Matthias Crauwels |
Deep dive into MySQL’s connection handling mechanisms for optimal connection pooling and improved concurrency. →
By Ayrton |
Learn how we utilized Markdoc to create custom, extendable product onboarding at PlanetScale. →
By PlanetScale |
Compare PlanetScale’s multi-cloud MySQL platform built on Vitess, with Amazon Aurora, one of AWS’s managed relational database services. Discover the strengths, features, and benefits of each platform to choose the best fit for your database needs. →
By PlanetScale |
Compare PlanetScale’s multi-cloud MySQL platform built on Vitess, with Amazon RDS, AWS’s managed relational database service. Discover the strengths, features, and benefits of each platform to choose the best fit for your database needs. →
By Nick Van Wiggeren |
We are adding vector storage and search to MySQL, enabling you to use PlanetScale for your AI use cases. →
By Jonah Berquist |
Not sure when to shard your MySQL database? This article covers when you should consider horizontal sharding as a scaling strategy in MySQL and some other scaling options before then. →
By Brian Morrison II |
Explore what to consider when deploying databases to Kubernetes, and how PlanetScale utilizes Kubernetes and Vitess to run hundreds of thousands of databases. →
By Liz van Dijk |
Grasping when and how to shard, selecting the ideal shard keys, and managing cross-shard queries effectively can prove difficult even for seasoned engineers. Learn how to do this, and more in this tech talk. →
By Taylor Barnett |
Learn how to use the new PlanetScale Netlify integration to simplify the process of wiring up a database to your Netlify applications. →
By Brian Morrison II |
Learn how to build virtual relationships between tables in PlanetScale while using the Drizzle TypeScript ORM. →
By Lucy Burns, Taylor Barnett |
Historically, there has been the belief that you cannot horizontally scale and shard MySQL, learn how Vitess has made MySQL sharding at the database layer a reality. →
By Shlomi Noach |
Why PlanetScale deploys branch changes near-atomically, and how it applies concurrency and dependency resolution without impacting production databases. →