Quality attributes drive architecture
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
explain why quality attributes, not features, pick the architecture.
Planned topics
- Two systems with the same features can have very different structures because of their quality targets.
- Each attribute pushes the design a direction: availability toward redundancy, latency toward fewer hops.
- Attributes compete for the same budget, time, and complexity.
- Name the few that matter most; you cannot maximize all.
Draft outline details
Demonstration
order subsystem with one feature set and two target sets: "internal tool, 99%" versus "customer checkout, 99.95%", sketched as two different deployments.
Check your understanding
Why can't every attribute be top priority?
Show answer
They trade off and share a limited budget.
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.