Sugu Sougoumarane
960 posts

Sugu Sougoumarane
@ssougou
Head of Multigres @Supabase, Co-creator @vitessio



There are now 7M developers using @supabase Signups have been accelerating since the start of the year Our growth rate right now is as fast as it was during YC, except that we are doing it from a base of millions of developers instead of thousands


Today we had an outage that ran for 3h42m, affecting 4.92% of our customers. All systems in us-east-2 were affected. I'm sorry to everyone affected. There is no good excuse - you trust us with your infra and we need to do better. We already have mitigations in place and we're working on a post-mortem. We will post it in the next 12 hours.




@kellabyte Simple answer is no: You don't know if what you're reading has reached quorum. Any data that hasn't reached quorum can be rolled back if there's a failure. I've listed a few viable approaches here: multigres.com/blog/generaliz….


If you have consensus writes with agreement across all 3 nodes, a quorum (2 nodes) read would allow a slightly faster read path not waiting for the slowest node to respond while still guaranteeing read your own write semantics. Am I understanding this correctly?










this month the @supabase community are running meetups in 38 cities around the world:













