You build it, you run it
On This Lesson 4 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
describe what owning a service means.
Planned topics
- Owning means responsibility for the service in production, not only for the code you wrote.
- Ownership covers on-call, SLOs, dependencies, cost, security updates, and the roadmap.
- The owning team feels the pain of its own failures, which drives better design.
- Ownership is shared and documented: an ownership page with names, contacts, and links.
- "I wrote it" is history; "I answer for it" is ownership.
Draft outline details
Demonstration
an ownership page outline: purpose, owners, SLOs, dashboards, runbooks, dependencies, cost, risks, debt.
Check your understanding
Name three things ownership includes beyond code.
Show answer
For example on-call, SLOs, dependencies, cost.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.