I only recently regained the ability to write long form.
I had an accident and fractured the metacarpal bone of my left index finger, needing screws to help repair it.
I promise some new content is coming, more on databases... in a couple more weeks.
What if the database had no idea what your WHERE clause clause actually meant until it had already dragged every single row off disk into memory? That used to be the default, ages ago. The storage layer was just a dumb block server handing your scan operator the pages to
I've been thinking about what the bottom of a database should look like if we stop asking it to understand the database. That sounds a bit backwards, so let me be more specific. Most databases make an early decision about the shape of the world. Rows belong to
We've built one Constellation: a few tens of thousands of machines, a ledger, a flock of schedulers, an autoscaler, identity, the works. Now you have more than one, because you have more than one region, or you've grown past what a single failure domain should hold.
Way back in the object-model post I made a point of saying orbit-core has no I/O, no network, no disk, just types and the functions over them, and in the ledger post I kept calling it an append-only, replayable log. Those weren't aesthetic preferences.
