Personally, I am quite impressed by the new serverless database offerings (PlanetScale, Neon.tech, Turso etc.), but incidents like this give me pause and make me wonder if I am better off sticking to e.g AWS Aurora and paying fix fees.
I use PlanetScale as well and have had a great experience so far! But honestly I have doubts whether it's the right technical choice to use a startup/scaleup for arguably the most mission critical part of my application.
Side note: I also had to figure out the ways in serverless/PlanetScale's MySQL is different (e.g. you can't have foreign keys, you can't create triggers). On the whole, foregoing these features for serverless makes it worthwhile though.
4 comments
[ 3.2 ms ] story [ 16.5 ms ] threadPersonally, I am quite impressed by the new serverless database offerings (PlanetScale, Neon.tech, Turso etc.), but incidents like this give me pause and make me wonder if I am better off sticking to e.g AWS Aurora and paying fix fees.
Side note: I also had to figure out the ways in serverless/PlanetScale's MySQL is different (e.g. you can't have foreign keys, you can't create triggers). On the whole, foregoing these features for serverless makes it worthwhile though.
EDIT: oh nvm they literally just announced foreign key support: https://planetscale.com/blog/challenges-of-supporting-foreig...