Multigres: Vitess for Postgres
supabase.com
Multigres: Vitess for Postgres
1–10 of 19 posts
Re: Multigres: Vitess for Postgres
#2Hello HN, co-creator of Vitess here. The goal of Multigres is to build an open source adaptation of Vitess for Postgres.
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.
Re: Multigres: Vitess for Postgres
#3[deleted]
Re: Multigres: Vitess for Postgres
#4Hello HN, co-creator of Vitess here. The goal of Multigres is to build an open source adaptation of Vitess for Postgres. 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…
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.
Re: Multigres: Vitess for Postgres
#5Hello HN, co-creator of Vitess here. The goal of Multigres is to build an open source adaptation of Vitess for Postgres. 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…
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 :).
Re: Multigres: Vitess for Postgres
#6Hello HN, co-creator of Vitess here. The goal of Multigres is to build an open source adaptation of Vitess for Postgres. 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…
Interested to know how it compares with PgDog: https://pgdog.dev/
Re: Multigres: Vitess for Postgres
#7Hello HN, co-creator of Vitess here. The goal of Multigres is to build an open source adaptation of Vitess for Postgres. 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…
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
#8Hello HN, co-creator of Vitess here. The goal of Multigres is to build an open source adaptation of Vitess for Postgres. 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…
This is super interesting - will you be open to contributions here?
Re: Multigres: Vitess for Postgres
#9Hello HN, co-creator of Vitess here. The goal of Multigres is to build an open source adaptation of Vitess for Postgres. 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…
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.
Re: Multigres: Vitess for Postgres
#10I don’t know if this is a question for you or for the Supabase leadership team. But, what is the primary reason for building something “new” instead of using the tools already existing in the Postgres ecosystem like Citus or pgdog?
What are the gaps in those which you expect to solve with Vitess for Postgres?