Viewing profile — bddicken

pgBaseBackup seems very cool. It's great that they got support to continue building. We just don't use it presently.

Neki will support cross-shard ACID transactions with a combination of an external transaction coordinator and some changes to PostgreSQL itself to support this (either by engine mo…

Exactly. When you have a router + query parser in front of the db nodes, the burden of managing multiple versions simultaneously can be taken out of the app and into the database l…

Broadly for Pg, minor version upgrades are straightforward as the data on disk is guaranteed to be compatible. All it takes is a restart or switchover to upgrade. Major versions ar…

What I emphasized in this article (author here) is scaling postgres backups. This works because there's already rock-solid systems built into postgres + surrounding tooling to buil…

Author here, thank you. Technically, they are using js + gsap + svg embedded i the article with iframes. Process-wise, I drafted most of them as static images in excalidraw, passed…

Very welcome

Yep! https://vitess.io/docs/reference/features/distributed-transa...

We have tons of customers who do exactly this. It's great. Sharding is for customers who out grow this path.

A lot of what you're referring to is dictated by the sharding strategy. Vitess and Neki both let you configure this via the VSchema / data topology (That's what I'm getting at here…

You should read through those articles.

> So an extreme example is OpenAI needing 50 replicas, but we're doing five blades ... err, we're doing 768 servers because the need arose "pretty quickly"? If you read the OpenAI …

Hey, author here. Technically, they're powered by js + gsap + svg. Process wise (for most of them) I sketched them out in advance in excalidraw for figure out layout, then passed t…

Spreading requests out across hundreds, thousands, and in some cases even more is precisely what is done in the industry for big databases! Good examples: cashapp: https://code.cas…

Caching at all levels is key to good db performance (cpu cache ram disk). CPU cache optimization is not my area of expertise, but I did write another fun article on io devices and …

Hey, I wrote this! Sharding is cool and foundational to making the internet work. I'm around to answer Qs.

It may not have the popularity it once did, but MySQL still powers a huge % of the internet.

What about spanner specifically benefits from random ids over sequential ones?

Simple sequential IDs are great. If you want UUID, v7 is the way to go since it maintains sequential ordering.

+1

I've also written about sharding. https://planetscale.com/blog/database-sharding

B+trees combined with sequential IDs are great for writes. This is because we are essentially just appending new rows to the "linked list" at the bottom level of the tree. We can a…

It's really just a matter of tradeoffs. B-trees are great, but are better suited for high read % and medium/low write volume. In the opposite case, things like LSMs are typically b…