JD talks with Sugu Sougoumarane, Head of Multigres at Supabase about one of the biggest engineering challenges facing large PostgreSQL deployments: how do you scale beyond a single database without replacing PostgreSQL?
Drawing on his experience building Vitess and now leading Multigres, Sugu explains why PostgreSQL is reaching a new stage of growth and why scaling it requires much more than simply sharding data. Together, he and JD explore the architectural decisions behind distributed transactions, resharding, consistency, and the infrastructure needed to help PostgreSQL scale while preserving what already makes it successful.
Whether you're building high-growth applications, planning for larger PostgreSQL deployments, or interested in distributed database architecture, this conversation offers a practical look at the challenges and tradeoffs behind scaling PostgreSQL without replacing it.
📬 Sugu Sougoumarane: https://www.linkedin.com/in/sougou/
The thread discusses the challenges of scaling PostgreSQL without replacing it, featuring insights from Sugu Sougoumarane of Supabase. The conversation covers architectural decisions, distributed transactions, and infrastructure needed for scaling. It highlights practical challenges and tradeoffs in distributed database architecture.
This is exactly the kind of engineering discussion I like - less hype about "just use distributed systems" and more about the actual tradeoffs that come with scaling something people already rely on.