Production Fundamentals

What makes production different from every environment you can reason about locally — real traffic, real data, real failure, real cost, and continuous change — and what DevOps actually means once it stops being a job title.

What Production Engineering Is

The discipline of making software operable under real traffic, real data, real failure and continuous change.

Q · What is the actual discipline here, once you remove the tool names?
What DevOps Actually Means

A set of practices for reducing the distance between building software and operating it — not a team, and not a job title.

Q · What does DevOps mean, given that it is now also a job title, a team name and a tool category?
Why Local Success Predicts So Little

Everything that makes production hard is absent from the environment where the code was written and reviewed.

Q · It works locally and in staging. What is production going to do that neither of those did?
The Production Loop

Code to build to artifact to release to deploy to observe to incident to learn — and why it is a loop rather than a line.

Q · What is the full path from a commit to a running system, and where does it close?
Shared Ownership

Who is responsible for a service in production, and why that answer has to be a specific team rather than everyone.

Q · Who owns this service in production, and what does owning it actually oblige them to do?
From Developer to Users

The full path a change travels, as a model you can debug against when something in it goes wrong.

Q · What is the complete chain between a developer and a user, and why is knowing it a debugging tool?
What Can Fail Between Commit and User

A catalogue of delivery failures, arranged by where in the chain they happen and what they look like from the outside.

Q · When a change does not reach users correctly, what are the actual candidate causes?