The archive
Comic cover for issue 011: The Microservice That Wasn't
Issue #011
Developer Diaries 7 min read· 28 Feb 2026

The Microservice That Wasn't

Fourteen services, four engineers, one shared database. A cautionary tale about copying architecture from companies a hundred times your size.

Share
The strip
Panel 1 · The diagram
Fourteen boxes. Beautiful. Very Netflix.
Panel 2 · The reality
Four engineers. One database. Fourteen deploy pipelines.
Panel 3 · The fix
Three services. Nobody missed the other eleven.

Architecture is a solution to an organisational problem. Microservices exist so that independent teams can deploy independently. With four engineers there are no independent teams — only one team paying fourteen times the operational overhead.

The tell was the shared database. Every service read tables owned by other services, which meant no service could actually be deployed independently. They had the cost of distribution with none of the benefit.

Microservices are an organisational tool. If you have one team, you have one service.

We merged down to three services along genuine ownership lines, keeping the boundaries the team actually argued about. Deploy time went from thirty-five minutes to four.

Distribution cost is real. Distribution benefit is conditional.

Nobody mourned the eleven services. What they mourned, briefly, was the diagram — it had looked so much like a real company.

CTO takeaway

The lesson, minus the scar tissue.

  • Pick service boundaries to match team boundaries, not domain diagrams.
  • A shared database means your services are one service wearing a costume.
  • Copying the architecture of a 5,000-person company is copying their problems, not their success.
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.