We migrated from PlanetScale to AWS Aurora v2

In January 2024, a decision was made to transition the production database from PlanetScale to AWS Aurora RDS due to several challenges and limitations experienced with PlanetScale, including the lack of a true serverless offering, opaque pricing, and insufficient control over server resources. Initially drawn to PlanetScale for its marketed serverless capabilities and simplicity of billing based on rows read or written, the database's shift in focus towards high-performance offerings, alongside unexpected increases in CPU usage and costs following an upgrade, prompted the move. Despite PlanetScale's initial benefits, such as ease of scaling and performance, its limitations—including no private network options, lack of foreign key support, and manual server monitoring—became increasingly problematic. The migration to AWS Aurora RDS, though complex and costly, was seen as a necessary step to accommodate the company's growth, offering advantages like auto-scaling, private networking, and multi-AZ failover, despite requiring additional planning and optimization efforts.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.