


Vitess for Postgres


@multigres will land on supabase early next year features: ◆ Sharding ◆ Local NVMe disks ◆ Cross-zone failover ◆ Automated Backups ◆ Built-in Observability ◆ Change Data Capture ◆ Built-in Connection Pooler ◆ Built-in Database Protection ◆ Migrations across PG versions

looks like @cognition's DeepWiki bots found the @multigres repo not bad:

at @supabase we're building: ◆ a new storage engine for Postgres ◆ an open source sharding engine for Postgres ◆ an open source ETL engine for Postgres ◆ an FDW extension to query anything from Postgres we hire talented people who just want to build. come us ↓

Today's post: Discovery and Propagation. With this, we complete everything about the protocol part of Generalized Consensus. There are a few more advanced topics to cover: They are needed for running in production. multigres.com/blog/generaliz…

The next three sections of Generalized Consensus are advanced topics. For example, how do you change the durability rules? Just re-apply the governing rules to perform the change. Links are in 🧵.

The conclusion of the Generalized Consensus series is a recap of everything we covered. As a bonus, we propose a design to change Raft into a generalized solution. multigres.com/blog/generaliz…

I'll be at the Palo Alto meetup if you wanna chat @multigres
this month the @supabase community are running meetups in 38 cities around the world:

Today's Generalized Consensus post: Revocation and Candidacy, the prerequisites for a leader change. We explain how to revoke previous leaderships and recruit for a new candidacy. It's a bit complex, but there are plenty of animations to help you along. multigres.com/blog/generaliz…

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 🧵

Today's release of Generalized Consensus: Ordering Decisions. How do you safely handle multiple coordinators racing to take action? We explore term numbers, coordinators as separate agents, and lock-free approaches. multigres.com/blog/generaliz…

Sugu (@ssougou), the co-creator of Vitess, is leading Supabase to build @multigres: Vitess for Postgres

Multigres is the future of @supabase, scaling your database indefinitely. I spent a few days with the Multigres team. They have scaled some of the world’s largest databases. Now they are doing it for the postgres ecosystem. See how:

.@ssougou: “Postgres needs to win.” Brilliant talk on how @multigres will take Postgres to enterprise scale. Can’t wait for what’s ahead. #SupabaseSelect

Multigres Q&A with @kiwicopple and @ssougou #SupabaseSelect

Sugu Sougoumarane throwing done some super nerdy technical bits @supabase conference. He says that DBs often force companies to limit new features. He says Multigres will make that obsolete. Good thing I’m on supabase then! #SupabaseSelect