What to standardize
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
pick the few places where sameness pays and leave the rest to teams.
Planned topics
- Standardize at boundaries: interfaces, events, identity, security, observability, deployment.
- Leave to teams what is inside a boundary: internal design, many libraries, test style.
- Languages and frameworks are a poor first target; the pain is rarely there.
- Standardize where inconsistency hurts people who are not the owning team.
Draft outline details
Demonstration
a sorting table for Commerce 2030: API error format (standardize), event envelope (standardize), trace and log fields (standardize), internal package layout (leave), choice of mapper library (leave).
Check your understanding
Why standardize boundaries before languages?
Show answer
Boundary inconsistency hurts other teams and operations; language choice mostly affects the owning team.
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.