Feature Casualties of Large Databases
Databases shed important RDMS features as they get big. Examining why this tends to be the case, and some ideas for preventing it.
I'm Brandur. This site is where I publish words and photos. The section updated most often is atoms , short multimedia particles reminiscent of a Twitter feed. I update my now page monthly according to what I'm working on and thinking about. I publish a newsletter as often as I can.
Visit brandur.org → RSS feedOn Hacker News May 2017 – Aug 2026
Software Engineering 27Databases & Data 20Tech Industry & Business 7Systems & Performance 6Career & Management 4Web & Frontend 3
Databases shed important RDMS features as they get big. Examining why this tends to be the case, and some ideas for preventing it.
It’s already been a great reading day for retrospectives on the last ten years / predictions for the next. Here’s to hoping that everyone had a good break (or at least a few days off), set or didn’t set resolutions, and is refreshed and ready for what comes next.
Building a robust background worker system that leverages transactional isolation to never work a job too early, and transactional durability to never let one drop.
How Postgres’ concurrency model coupled with long-lived transactions can degrade the performance of indexes on hot tables in your database.
Tracking improvements to Postgres partitioning since 2017. In just five years it’s gone from a non-feature to a very good one.
I've been playing around with SQLite the last couple of days. I thought I knew a little about SQLite, but I didn't, and am getting my remedial education through an accelerated gauntlet. Some of what …
Stripe’s API got a new major version, and no one noticed.
A workaround to get nice stack traces for errors in Go.
Offset pagination gets a bad rap because it’s backend inefficient, but it’s actually a nice feature from a consumer’s perspective. How to bring those advantages to cursor-based APIs.