Designing for operations
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
treat operations as a design input, not an afterthought.
Planned topics
- Operations is where the design is tested every day; ask the operations team early.
- Design questions: who detects a failure, who fixes it, how do they see it, what is the runbook.
- Include operability requirements: observability, deployability, recoverability, supportability.
- Operational acceptance criteria are written at design time and checked before handover.
Draft outline details
Demonstration
an operability checklist per component: health endpoint, logs, metrics, alerts, runbook, owner, backup and restore, on-call.
Check your understanding
When should operations be involved?
Show answer
From the start of design, not after go-live.
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.