Blog
Get the RSS feedIntroducing FastPage a new gem for ActiveRecord that speeds up deep pagination queries. →
Learn how PlanetScale uses a custom middleware to kill our Sidekiq jobs in production without relying on deploys. →
Learn how PlanetScale enables databases to seamlessly fit into the DevOps lifecycle. →
Learn how PlanetScale protects against downtime due to human error system immaturity and app issues. →
Learn how to delete data in large Rails apps with destroy_async delete destroy and scheduled cron jobs. →
Handle MySQL increment counter bursts with the Slotted Counter Pattern →
Learn how we leveraged Vitess ACLs and VTTablet to build our password roles functionality →
Learn how to safely drop tables in MySQL by checking if the table is still in use and how PlanetScale makes this process much easier. →
Learn how to create a more reliable workflow with Temporal and PlanetScale →
Learn how you can manage database access with Teams and Directory Sync →
Learn about how we built the new in-app system status using Vercel edge functions and StatusPage →
Learn how database indexes work under the hood and how they can be used to speed up queries →
Learn how to quickly get up and running with the PlanetScale CLI. →
In the final installment of the consensus algorithm series we pull everything together with some final thoughts. →
We’ve updated our Deploy Request UI to alert when a schema change could produce unintended changes →
In part 7 of the Consensus algorithm series we combine everything we’ve worked at to cover propagating requests →
Learn about what was just released in Vitess 14 →
Vitess is a database proxy that creates an illusion of a single database when in reality the query is sent to multiple MySQL instances. →
In part 6 of the Consensus algorithms series we look at how to handle request completions →
Insights gives you a faster way to debug and monitor your PlanetScale database queries →
Use PlanetScale Connect to easily perform ELT (Extract, Load, Transform) actions on your data to fulfill your application needs. →
Put your data where your users and applications are. →
An exploration of the current landscape of schema change methodology and what the future should look like. →
In part 5 of our consensus algorithms series we discuss how we handle race conditions and forward progress requirements. →