Great comparison, but i feel like it would be fair to mention support for foreign key constraints in the overview table (which planetscale doesn‘t have, afaik)
The “Trusted by” page has some pretty impressive flagship companies (GitHub, Slack, Square, AirBnb). Is anyone familiar with the role in which Planetscale is used at those companies? (Unless that is advertising users of vitess vs the hosted offering).
If one only needs a database, it's probably not worth to go to AWS due the unnecessary complexity.<p>Now if you're using other services, be aware of egress costs, which are not mentioned in the article.
Does anyone have a good reference to a comparison of the two products that isn't written by someone with a strong financial incentive for you to pick one over the other?
The main issue that doesn't seem to be reflected here is that it's really hard to have a database and your application in different locations. Latency and security are big components in the general equation and both might be affected by this.<p>(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.)
This is how you beat Amazon/AWS, you go for the 40 percent where they fall behind in their products and make it better. They have a broad set of tooling not a particularly deep set of tooling.