You already know: every case in this bank. This capstone puts them together for Atlas, the learning platform used as the running example throughout the course. It is written as a design review for leadership: not only what the system looks like, but what it costs per student, what fails first, how quality and safety are guaranteed as it changes weekly, and in what order to build it. Each box in the architecture is a case you have already studied; this lesson is about how they fit, where the money goes, and how to defend the plan.
How to read this lesson. No code, on purpose. Numbers are assumptions and illustrative prices; the method of deriving them is the point.
1. The prompt, and the questions that change the design
A mid-level answer draws a large diagram of services. A staff answer starts from the four questions leadership must answer: what success means per product area, what the money allows per student, what must never fail, and what order to build in. Those produce a metric ladder per area, a cost model per active student, cells, failover and degraded modes, and a phased roadmap.
Assumptions you state: