Episode goal: name the problem the rest of the series solves — horizontal concerns duplicated across services — so the viewer feels the pain before we offer the cure.
Cold open
On camera: “Your first microservice is a joy. Your tenth is a warning. Let’s talk about what changed.”
Setup
Voiceover: “Every service needs the same non-business things: knowing who’s calling, logging the same way, retrying safely, resolving the tenant, returning the same error shape. None of that is your product. All of it is horizontal — it cuts across every service.”
On screen
Two columns titled Business logic and Everything else. Drag items from a service into the right column: auth, logging, correlation IDs, retries, tenancy, validation, i18n, error envelope. The right column fills up; the left has one line.
The reveal
Voiceover: “Now copy that right-hand column into ten repositories, written ten slightly different ways, by ten people, over two years. That’s not architecture — that’s ten liabilities.”
Demo
Grep the same concept (say, reading the current user or building an error response) across several real service repos; show the near-duplicate-but-drifted implementations side by side.
Cost line
Lower third: “A security fix becomes a ten-repository pull request.” Beat. “That’s the tax.”
Reframe
Voiceover: “The cost of microservices is rarely the services. It’s the duplication of everything around them. Fixing that needs two ideas: a cleaner definition of what a service is, and a home for all the horizontal stuff.”
Cliffhanger
“Next: the first idea — a service is a contract, not a codebase.”
Recap card
“Microservices multiply the places where cross-cutting concerns get re-implemented. That duplication is the real cost.”
Companion reading: Why microservices — and what they really cost