Gated Deployments and Schema Revert have changed how we approach database releases because they give us more control over when the risky part actually happens. With a long migration, PlanetScale can do the copy and synchronization work up front while we decide when to trigger the final cutover. If a deployment causes trouble afterward, certain deploy requests can still be reverted within a 30-minute window, and when the schema change allows it, writes can be preserved. That makes release planning feel far less binary—we’re no longer forced to choose only between “ship now” and “wait for another maintenance window.” Query Insights has been just as valuable. It puts latency, query count, rows read and written, full table scans, and anomalous queries in one place, and it overlays deploy requests on the same timeline. That makes it much easier to tell whether a schema change actually caused a slowdown or whether it simply happened around the same time. We’ve also used the schema recommendations to catch missing indexes based on real traffic. In one case, what initially looked like a compute problem turned out to be a query doing far more work than it needed to.

It is probably the best MySQL as a service platform in existence. Modern, blazing fast, easy to use from any languages, easy to scale and implement.

In particular, I enjoyed deploy requests. My team was easily able to collaborate with deploy requests and make changes, much like git