Viewing profile — sougou

This is the Kubernetes Operator for managing deployments of Multigres across multiple failure domains.

Hi HN, this is a series on a way to generalize consensus protocols and how to adapt them to existing systems. This is part 7: Discovery and Propagation. With this, we complete ever…

Hi HN, this is a series on a way to generalize consensus protocols and how to adapt them to existing systems. This is part 6: It covers Revocation and Candidacy, the prerequisites …

Hi HN, this is a series on a way to generalize consensus protocols and how to adapt them to existing systems. This is part 5: This one covers how to safely handle multiple coordina…

Hi HN, this is a series on a way to generalize consensus protocols and how to adapt them to existing systems. This is part 4: This one has a nice animation that shows how requests …

Hi HN, this is a series on a way to generalize consensus protocols and how to adapt them to existing systems. This is part 3: Governing Rules. This is the foundation for the rest o…

Hi HN, this is a series on a way to generalize consensus protocols and how to adapt them to existing systems. I've released two parts so far. They explain the problem and the requi…

I oversaw this work, and I'm open to feedback on how things can be improved. There are some factors that make this particular situation different: This was an LLM assisted translat…

We absolutely need this!!! I vote yes :).

You won't believe what a nightmare it was to work with transactionless DDLs in MySQL. Transactional DDL will be a dream come true for Vitess: we can throw away all the hacks we had…

The Vitess architecture was traditionally built in a database agnostic fashion. Most of its features should port smoothly over to Postgres. The cool features that I can think of: A…

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.

PgDog looks very similar to Vitess in terms of approach.

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…

Hello 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 …

It's not just failure detection. A write to EBS is at least two additonal network hops. The first one is to get to the machine for the initial write, and the second is for that wri…

The way to reason about this is: If a customer had a huge business, what key would they shard by? Then choose that as the sharding key for all customers.