5 ms·
Multigres is the one that comes to mind
by jbonatakis 22d ago
Multigres is the one that comes to mind
- kelp 22d agoOnce they implement sharding...
- jbonatakis 22d agoYet. But it’s built by the guy who created Vitess and cofounded PlanetScale, so while it doesn’t have sharding implemented at the moment I think it would be foolish to discount it. Plus it’s open source.
- uberman123 22d agoSugu? The guy that "barely worked" and "shipped nothing at PlanetScale" according to Planetscale's CEO?
- karlmush 22d agoAnyone who has worked with Sugu knows this simply isn’t true. Sam Lambert is lying.
- samlambert 22d agoevery metric we have proves otherwise
- samlambert 22d agoWe literally have the counterfactual of the old product and company before he left. We can fully discount Multigres doing anything.
- deleted 22d ago[deleted]
- kelp 22d agoThe PlanetScale team spent years improving Vitess with lessons learned from many different high scale customer workloads. We continue to invest in and improve Vitess. It's a substantial and growing part of our business. Vitess today is not the Vitess of 2021. About 70% of the current codebase was written in the last five years, based on lessons we learned running it at scale. Neki is built for Postgres from the ground up, by the engineers who did that work. On the Multigres comparison, I'll admit we get a bit salty, mostly because "Vitess for Postgres" invites the comparison. But to date there's no public evidence of a working sharding implementation in Multigres. Their sharding design doc landed this week, and it lists cross-shard query planning and resharding execution as explicitly out of scope. Neki does sharding today, including online resharding that switches traffic without a maintenance window. It isn't open source, but you can spin up a cluster and try it yourself.