Cost as a design input
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 cost as a quality attribute designed in from the start.
Planned topics
- Cloud cost is a result of design choices: compute shape, data movement, storage, redundancy.
- Cost is variable and usage-driven, so it can surprise as easily as it can save.
- Compare options by total cost including operating effort, not only the price list.
- Surface the cost of each requirement (for example, a tighter RTO) to the sponsor.
- Cost and other qualities trade off; record the trade-off.
Draft outline details
Demonstration
two designs for the same requirement with their cost and risk, such as warm standby versus backup-restore.
Check your understanding
Is cost only a finance concern?
Show answer
No; design choices create it, so architects own part of it.
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.