Topic 0.1
Why Cloud Computing Exists
In one line
Owning physical servers means paying for peak capacity you rarely use and waiting weeks to get more — cloud computing rents exactly the capacity you need, the moment you need it, and nothing more.
Think of it like this
Owning a car you drive twice a year versus calling a taxi exactly when you need one — owning means paying for insurance, maintenance, and parking every single day regardless of use; renting on demand means paying only for the exact trips you actually take. Cloud computing is renting infrastructure the same way.
Key ideas
- 01
Before cloud computing, running a real application meant physically buying servers, provisioning them in a data center you managed (or paid someone else to manage), and living with whatever capacity you bought — running out of capacity during a genuine traffic spike meant a real, weeks-long wait to order, receive, and install more hardware.
- 02
AWS (and cloud computing generally) replaces that ownership model with ON-DEMAND, PAY-AS-YOU-GO infrastructure — you provision a server (an EC2 instance, Phase 2) in minutes, not weeks, and you pay only for what you've actually used, scaling up during real demand and back down afterward, with zero physical hardware ever purchased or owned.
- 03
This eliminates CAPACITY PLANNING as a genuinely high-stakes guessing game — historically, a team had to predict future demand months in advance and buy hardware accordingly, risking either overspending on unused capacity or, worse, running out during a genuine success (a viral product launch overwhelming under-provisioned physical servers). Cloud infrastructure lets capacity follow ACTUAL, real-time demand instead.
- 04
AWS specifically was the first major cloud provider (launched in 2006) and remains the largest — its own infrastructure spans GLOBAL REGIONS (Topic 0.2 covers this directly), letting you run infrastructure physically close to your actual users anywhere in the world, something a single company-owned data center could never practically replicate on its own.
- 05
The one-sentence pitch you should be able to give in an interview: 'Cloud computing replaces buying and owning physical infrastructure with renting exactly the capacity you need, on demand, paying only for actual usage — removing capacity planning as a high-stakes guess and letting infrastructure scale with real, live demand.'
Code & diagrams
The fundamental trade this entire course builds on top of.
Explain it without notes
Why was capacity planning such a high-stakes guess before cloud computing existed, and what specifically changed with on-demand infrastructure?
Give one concrete reason a global company would genuinely benefit from AWS's multiple physical regions, beyond just 'more servers.'
Practice
Think of a real or hypothetical product that experiences a genuine, predictable traffic spike (a shopping site on a big sale day, a tax-filing service near a deadline) and describe in one sentence how on-demand cloud capacity specifically helps versus fixed, owned hardware.
Look up (or recall) roughly how many AWS regions currently exist worldwide, and name one genuine reason a company might deliberately choose to run infrastructure in more than one.
Trade-offs
- ↔
On-demand cloud infrastructure removes the capacity-planning guess, but it also means costs can genuinely grow unexpectedly if usage isn't monitored (Phase 7 covers cost optimization directly) — a fixed, owned server has a predictable, capped monthly cost no matter how it's used; cloud infrastructure's cost scales directly with actual usage, which is a genuine benefit under normal conditions but requires real, deliberate monitoring to avoid a surprising bill from a misconfigured or genuinely runaway resource.
Done when you can
I can explain why capacity planning was such a high-stakes guess before on-demand cloud computing.
I understand the pay-as-you-go model and how it changes the cost/risk profile of running infrastructure.
I can give a genuine, concrete reason a company would want infrastructure in more than one geographic region.