Sugu Sougoumarane
@ssougou
Head of Multigres @Supabase, Co-creator @vitessio
multigres.com is up 🎉. Up next: some cool technical blogs about innovations in Multigres.
Last night was a blast – a fantastic group of database engineers and researchers got together to talk shop and have fun! Over three hours of flowing simultaneous conversations – it was really hard to wrap it up. The idea was simple – swap a Michelin-star private room dinner for…
We intend to make @multigres work with @orioledb.
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.
This turned out to be very technical. We went pretty deep into the Postgres durability challenges, and how @multigres plans to tackle them.
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
MVP project plan for @multigres is out. Things may look slow, but substantial progress has been made under the covers. github.com/multigres/mult…
Vitess is coming to Postgres! @ssougou, the co-founder of @PlanetScale and co-creator of @vitessio talked with me about his move to @supabase and the creation of @multigres. Certainly a timely interview 👀 Link the next tweet.
Those of you watching @multigres, I've started trickling in some changes. Also, discussions are open if you have questions or comments.
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've experienced this twice so far: - Relational algebra can be used to unify multiple relational databases, which led to the Vitess sharding scheme. - Consensus can be split into smaller concerns, which led to the Vitess durability policies.
There is tremendous joy that can be extracted from breaking down technology to its fundamental first principles. At first it is blurry, confusing and filled with vague abstraction. Once understood, it is clear as day. Only then an engineer can use the technology effectively.
Uncle Bob may be on to something. If we were to think from first principles, we'd either design a language or api that directly controls the primitives of a database, or one that is readable. SQL is neither. Have you seen those one page queries?
Morning bathrobe rant about SQL.
If you're avoiding sad people, you're probably avoiding your own sadness.
the best way to be happy is to avoid sad people
Is there a Raft implementation for Postgres? If so, do people use it?
I remember having one of the most interesting conversations about consensus algorithms with someone from @fauna at HPTS. But I don't remember who it was.
Throughout the life of @vitessio, we had to fight hard against this trend of separating compute from storage. We knew this would hurt OLTP performance. What @PlanetScale managed to pull off makes me so proud. Maybe someday, I'll write about how we did it.
Why settle for slow? Our latest interactive blog covers the history of IO devices, how storage works in the cloud, and why separation of storage and compute is bad for OLTP databases.
"More Cowbell", by @PlanetScale
⚡ Introducing PlanetScale Metal ⚡ - Blazing fast NVMe drives - Unlimited IOPS - Drastic reductions in latency - And best price:performance ratio of any database available in AWS or GCP
About a month ago @tuple set out to give away three $10,000 vacations to open source developers. After receiving 15,000 votes from almost 5,000 people, we're excited to announce the winners! 🥁🥁🥁 Congratulations to @teej_dv, @ATechGirl, and @posva!
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 planetscale.com/blog/consensus…
