Using PlanetScale for db management is like using an iPhone after being accustomed to a Treo. The experience is just better in every way.
Congrats to the PlanetScale team!
Would love more details tbh, but will be watching regardless.
[0]: https://supabase.com/blog/multigres-vitess-for-postgres
[1]: https://pgdog.dev
Does this new PostgreSQL offering share any heritage with Vitess or is this an entirely new piece of technology, or based on other components that PlanetScale have written since the Vitess days that aren't direct descendants?
Update: to answer my own question https://planetscale.com/blog/planetscale-for-postgres#vitess...
> Vitess’ achievements are enabled by leveraging MySQL’s strengths and engineering around its weaknesses. To achieve Vitess’ power for Postgres we are architecting from first principles. We are well under way with building this new system and will be releasing more information and early access as we progress.
When data grows beyond a single machine, the hard work begins. Distributed systems sacrifice features like complex joins, extensions, and strong consistency. Maybe they should get Jepsen to poke at their setup. Who can show us what we lose compared to standard Postgres?
I get it, I'm a small fish trying to pay a little as possible for fully managed postgres (or MySQL before I switched to Postgres when I moved to Neon) to run my small, bootstrapped company with spiky [0] but fairly predictable load.
Best of luck to PlanetScale with this new offering, one day I hope I can use them again. I enjoyed the product and the support was great.
[0] I write software for food festivals, 9 months out of the year there is no traffic, ~2 months of the year there is a tiny trickle, ~3 weeks seeing high (but not "high" by any definition) and then 1-5 days (depending on how long the event is) there is a good deal of load but still not more than the lowest tier can handle most of the time. Like I said, I'm a _small_ fish and I don't expect them to cater to me, I just know what I want and almost no one provides it directly.
The future sharded version will also be based on Postgres directly, and will be as compatible as possible. We're not looking to just speak the PG wire protocol to a different backend store.
...Depending on how many tenants that is, Turso may fit your use case.
I could make my application multi-tenant in the application code but that would require a lot of refactoring and testing. It's possible but it's a big lift to do that. If I could do that, I'd have much more flexibility. I don't think compliance will ever be an issue for me so that isn't holding me back.