sougou

5 ms·

1.
Show HN: Multigres Kubernetes Operator(github.com)
7 points by sougou 6mo ago|0 comments
2.
by sougou 11mo ago
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 everything about the protocol part of Generalized Consensus. The
3.
Generalized Consensus: Discovery and Propagation(multigres.com)
2 points by sougou 11mo ago|1 comments
4.
by sougou 11mo ago
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 for a leader change. We explain how to revoke previous leade
5.
Generalized Consensus: Revocation and Candidacy(multigres.com)
1 points by sougou 11mo ago|1 comments
6.
by sougou 11mo ago
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 coordinators racing to take action. We explore term numbers, coordin
7.
Generalized Consensus: Ordering Decisions(multigres.com)
1 points by sougou 11mo ago|1 comments
8.
by sougou 11mo ago
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 get fulfilled. One of our goals is to make this work for Pos
9.
Generalized Consensus: Fulfilling Requests(multigres.com)
1 points by sougou 11mo ago|1 comments
10.
by sougou 11mo ago
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 of the series. We'll be repetitively applying these rule
11.
Generalized Consensus: Governing Rules(multigres.com)
1 points by sougou 11mo ago|1 comments
12.
by sougou 11mo ago
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 requirements. You can follow the link to the second part fro
13.
Generalized Consensus: Defining the Problem(multigres.com)
2 points by sougou 11mo ago|1 comments
14.
by sougou 1y ago
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 translation of the C parser from Postgres, not something from t
15.
by sougou 1y ago
We absolutely need this!!! I vote yes :).
16.
by sougou 1y ago
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 to do for MySQL's sake. I also see such a clean 2
17.
by sougou 1y ago
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 formal sharding scheme based on relational foundations, a f
18.
by sougou 1y ago
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.
19.
by sougou 1y ago
PgDog looks very similar to Vitess in terms of approach.
20.
by sougou 1y ago
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 :).
21.
by sougou 1y ago
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 is to fork and retrofit. This will give us immedate res
22.
Multigres: Vitess for Postgres(supabase.com)
49 points by sougou 1y ago|17 comments
23.
by sougou 2y ago
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 write to be propagated to another machine for durability.
24.
by sougou 6y ago
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.
25.
Pitfalls of Isolation Levels in Distributed Databases(planetscale.com)
2 points by sougou 6y ago|1 comments
26.
Consensus Algorithms at Scale – Part 3(planetscale.com)
6 points by sougou 6y ago|0 comments
27.
The rules of consensus algorithms inspired by scaling YouTube(planetscale.com)
6 points by sougou 6y ago|0 comments
28.
by sougou 6y ago
This is still in our plans. We're likely to launch by end of year.
29.
by sougou 6y ago
We've come a long way in Vitess in terms of usability. And we're adding even more tooling to support onboarding and migrations.
30.
by sougou 8y ago
Github is evaluating Vitess. They'll probably talk about it if and when they deploy it into production.

More ›