Reviewing for complexity and operability
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
judge whether the team can build and run what they propose.
Planned topics
- Complexity is a cost: each new component, language, or pattern needs an owner and on-call.
- Ask whether a simpler design meets the requirement.
- Operability: who is paged, what dashboard shows health, how do you debug, how do you recover?
- Match the design to the team's capability, or note the gap.
Draft outline details
Demonstration
a table: proposed component, what problem it solves, a simpler alternative, who operates it, how failure is detected.
Check your understanding
What is the operability test for a new service?
Show answer
Who is paged, how failure is seen, and how it is recovered.
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.