The archive
Comic cover for issue 005: The Database Nobody Owned
Issue #005
Production Horror Stories 8 min read· 23 May 2026

The Database Nobody Owned

Six services wrote to it. Nobody could name its schema owner. Then the disk hit 98% on a Sunday morning.

Share
The strip
Panel 1 · Sunday, 09:12
Disk at 98%. Nobody on call knows why.
Panel 2 · 09:40
An audit table with 400 million rows. Added in 2021. By whom?
Panel 3 · 11:15
git blame returns a contractor who left three years ago.

Shared databases are the most comfortable bad decision in software. They're fast on day one, invisible on day ninety, and lethal on the Sunday your disk fills up.

This one had six writers. Two of them were cron jobs nobody had documented. One was a legacy PHP admin panel that the ops team believed had been decommissioned in 2023.

An unowned system doesn't fail slowly. It fails all at once, on the day you're least available.

The immediate cause was an audit table with no retention policy. The real cause was that no single team could tell you what the database was for, so no single team felt responsible for its health.

If you can't name the owner, you don't have a system. You have a liability.

We bought time with a partition drop, then spent six weeks assigning owners — not migrating, just naming. Ownership alone eliminated four of the six writers, because two of them turned out to be nobody's requirement at all.

CTO takeaway

The lesson, minus the scar tissue.

  • Every datastore needs a named owning team before it needs a scaling plan.
  • Retention policies are not optional. Unbounded tables are outages with a delay fuse.
  • Start migrations by assigning ownership. Half the problem disappears with the paperwork.
Comments

War Stories.

Survived something similar? Add it to the record — the best lessons in this archive came from other people's outages.

  • Priya · CTO, logistics startup

    We had the exact same Friday. Except ours was a DNS TTL of 86400 and we spent the weekend explaining caching to the board.

  • Marcus · Founder

    Read this on a Monday morning and immediately cancelled a rewrite. Three seams, not a clean slate. Thank you.

Never miss an issue

Get the next Chronicle in your inbox.

A comic, a story and a takeaway every other week. Written for founders who inherited a codebase they didn't choose.

Free forever. Unsubscribe in one click.

Related Chronicles.