This is very interesting, thanks for offering to answer questions. I'm curious of two things:
* Are you also considering going the Postgres extension route, like Citus? It is after all the best attempt at sharding Postgres so far.
* If you are willing to share, why not doing this from inside Planetscale? I assume it was at least considered over the years.
It will be a proxy layer. Since Vitess has proven itself with this approach, I don't see a reason to try anything drastically different.
As for Planetscale, I've posted my thoughts on X and LI :).
Interested to know how it compares with PgDog: https://pgdog.dev/
PgDog looks very similar to Vitess in terms of approach.
Re:Multigres: Vitess for Postgres
by parthdesai on Tuesday June 10, 2025 @01:00PM
(#44239015)
This is super interesting - will you be open to contributions here?
Of course, but not right away. We'd like to get the project to a decent stable state first. Then, we'll open it up.
Your unique advantage is you know Vitess super well. Your unique disadvantage is you know Vitess super well! Second system syndrome is real. Using as much Vitess as possible could help you guard against it.
Excited to follow your progress :)
In terms of project plan, we're still deciding. One option is to fork and retrofit. This will give us immedate results, but we'll be inherting quite a bit of legacy that we'll have to overcome later. The other option is to start with a clean slate and move pieces from the original Vitess code. This will ensure that Multigres has the Postgres DNA. We'll also avoid inheriting legacy features. Let us know your thoughts on this.
I'll try my best to answer any other questions you may have.