Cloud Economics Concepts
Understand concepts of cloud economics
What you will learn
- Explain the shift from capital expenditure (CapEx) to operational expenditure (OpEx) and its effect on cash flow.
- Identify what a total cost of ownership (TCO) calculation should include beyond the server's own price.
- Explain right-sizing resources as an ongoing process.
- Distinguish cost reduction from cost avoidance in a broader economic context.
Cloud economics does not mean "the cloud is always cheaper" — it provides tools and patterns that optimize cost if used deliberately. A common misconception is that moving to the cloud automatically saves money; the real benefit depends on how the workload is designed and continuously reviewed.
Core concepts
| CapEx vs. OpEx | Upfront capital spending versus operational spending that varies with consumption. |
|---|---|
| Total Cost of Ownership (TCO) | The full cost of running infrastructure, including electricity, cooling, space, and staff — not just hardware price. |
| Right-Sizing | Matching the size of a rented resource to actual measured usage, and reviewing it periodically, not just once. |
The CapEx model vs. the OpEx model
| CapEx (traditional data center) | OpEx (the cloud) | |
|---|---|---|
| Cash flow | A large payment upfront, before any actual use | Gradual payment alongside actual use |
| Risk of a wrong estimate | High — over- or under-provisioned capacity is a fixed sunk cost | Low — size can be adjusted later based on actual measurement |
The right-sizing cycle
Measure actual usage
Via CloudWatch or similar tools, over a long-enough period, not a single moment.
Identify over-provisioned resources
Instances consistently using a very small fraction of their capacity.
Adjust the size
Move to a more appropriate instance type, not necessarily just the cheapest.
Re-measure periodically
Usage changes as the product grows, so optimization is ongoing, not a one-time step to finish and forget.
What matters on the exam
- TCO includes hidden costs (electricity, cooling, space, staff), not just server price — the same idea as objective 1.1, but explored in more depth here.
- Right-sizing is not a one-time step done at migration — it's a continuous, recurring review.
"The cloud is always cheaper" is a wrong assumption
A workload designed without review (oversized instances running unnecessarily around the clock) can cost more than its on-premises equivalent. The real economic benefit comes from exploiting elasticity and continuous right-sizing, not from the migration itself.
Quick check
Answer in your head first, then reveal.
What does a TCO calculation include besides the server's price?Reveal the answer
Electricity, cooling, space, and staff.
Is right-sizing a one-time step done at migration?Reveal the answer
No — an ongoing, recurring process as usage changes.
Does moving to the cloud automatically save money?Reveal the answer
No — the benefit depends on workload design and ongoing review.
Sign in to track your progress on this topic.
Your next step
Read the lesson, then mark it complete
Sources
Used to verify the facts. The writing is original to Passuit.