https://vitess.io/docs/reference/compatibility/mysql-compati...
"We make some things easier for developers but you will have to deal with concurrent updates in your application"
edit: see the case studies linked here https://planetscale.com/enterprise
Now if you're using other services, be aware of egress costs, which are not mentioned in the article.
I think PlanetScale is built for someone who isn't using raw machines to build an app or running a dev-ops org.
Something like Vercel+PlanetScale is more along the lines of tooling you're likely to use (or Heroku if you're dealing with existing code).
The egress costs are rarely an issue for API endpoints, unless you're serving assets out of the hosts.
There's a million intranet-like workflow apps which don't need the additional headache of maintaining an RDS (or the skills to secure IAM). Mostly state machines with click-next-to-continue - Airtable probably hits the same demographic.
I think PlanetScale has got to work on their pricing model if the assumption is that it is ideal for that sort of an app (it's not "attractive" to switch right now & there's no pricing protection plans), but I'm not an economist or sales guy - like look at Google Fi bandwidth pricing for an example of where I overpay for data.
(This is the same reason why, although there are excellent Redis-as-a-service products, it's hard to justify to use them at all.)
