Shared nothing architectures are useless for 99% of the market and break compatibility with the single node databases.
Shared nothing architectures are useless for 99% of the market and break compatibility with the single node databases.
I’ve never had compatibility issues with single-node databases. It “just works” in the cloud and locally thanks to MySQL support in vitess.
I believe Neon will be one of the providers that sticks around to do this. Comparison is the thief of joy.
There is a ton of work internally that will improve the uptime as we get to GA.
https://vercel.com/changelog/vercel-postgres-is-now-availabl...
Anyone can claim this and LVM together 20 64TiB EBS volumes and put them on one big node. That's not sharding or bottomless.
Sharding and a shared nothing have incredible benefits to anyone who has a requirement for uptime, scalability, and cost reduction. We’ve avoided supporting parts of MySQL that make scaling worse and are working to add them back in ways that work, like FKs. In return for not supporting all MySQL features we hand back an immense amount in return. This is something our customers have been happy with.