I'm re-releasing the generalized consensus series one blog at a time for easier ingestion. Today, it will be the first two parts: Defining the Problem and Setting the Requirements. Links in 🧵
Joining Supabase
For some time, I've been considering a Vitess adaptation for Postgres, and this feeling had been gradually intensifying. The recent explosion in the popularity of Postgres has fueled this into a full-blown obsession. As these databases grow, users are going to
I'm starting a series of blog posts on consensus algorithms. My intent is to not only show that we're going to build something robust with @vitessio , but we're going to pull ahead with tricks that traditional systems like Paxos and Raft cannot achieve.
First @multigres blog is out. This is a teaser. We'll follow this with a series on generalized consensus and how we'll make it work with Postgres. multigres.com/blog/2025/07/2…
You didn't try the 3x approach I recommended? Also, Raft has one fundamental difference from Paxos: Raft is lock-based, and Paxos is lock-free. I explain why in part 5 of my blog:
New episode: "Multigres"
Nikolay and Michael are joined by @ssougou to discuss Multigres — a project he's joined Supabase to lead, building an adaptation of Vitess for Postgres!
🎧 postgres.fm/episodes/multi…
📺 youtu.be/KOepJivmWTg
I'm proud to announce that @ATechGirl has been named Tech Lead for vitess.io. Deepthi will now be the first line of contact for all technical and project related issues. Congratulations!
New @orioledb release: we added TPC-C benchmarks so you can be the judge on the performance
In case you're new to Oriole: it's a Postgres extension that replaces the default storage engine. GA coming soon.
Thanks to @zmagg's work from @SlackHQ, I was able to whip up these @PrometheusIO +@grafana graphs for @vitessio so easily. I'll be talking about these at the @Percona conference next week: "Observability features of Vitess".
It's a wrap!
This series shows a way to conceptualize consensus algorithms, where Paxos and Raft are a special case. But more flexible implementations are possible: @vitessio lets you specify arbitrary durability rules through plugins. @planetscaledata
