Why Cloud Computing? A Beginner’s Answer to the First Question I Had
What the cloud actually is, the six benefits AWS teaches in Cloud Practitioner, and why it’s worth learning as a student.
When I started studying for the AWS Cloud Practitioner exam, I realized I couldn’t answer a very basic question: why does anyone use the cloud in the first place? 🤔
Everyone says “move to the cloud,” but why? Companies ran their own servers for decades. What changed?
Here’s what I’ve learned so far, explained the way I wish someone had explained it to me.
First, what is cloud computing?
Cloud computing means using computing resources (servers, storage, databases, networking, software) over the internet, on demand, and paying only for what you use.
Instead of buying and running your own computers, you rent them from a provider like AWS, which runs huge data centers around the world.
💡 The analogy that made it click for me: electricity. You don’t build a power plant to turn on your lights. You plug into the grid and pay for what you use. Cloud computing does the same for computing power.
What it was like before the cloud
Imagine you’re launching an app. Without the cloud, you’d need to:
- Guess how many servers you’ll need
- Buy them upfront (expensive!)
- Wait weeks for them to arrive
- Find a room with power, cooling and security
- Hire people to maintain them
And if you guessed wrong? Too few servers and your app crashes when it gets popular. Too many and you’ve wasted money on machines doing nothing. 😬
The six benefits of cloud computing
AWS describes six advantages, and they come up on the Cloud Practitioner exam:
| Benefit | What it means in plain words |
|---|---|
| Trade upfront expense for variable expense | No buying servers upfront. Pay only for what you use, when you use it. |
| Benefit from massive economies of scale | AWS buys at a huge scale, so prices are lower than you could get alone. |
| Stop guessing capacity | Scale up when traffic grows, scale down when it drops, often automatically. |
| Increase speed and agility | New servers in minutes, not weeks, so you can experiment and build faster. |
| Stop spending money running data centers | Focus on your product and customers, not on racking hardware. |
| Go global in minutes | Deploy in Regions around the world to be closer to your users. |
Real examples that helped me understand
- 🛒 An online store during a big sale: traffic jumps for a few days. With the cloud, it can add servers for the rush and remove them after, instead of owning extra servers all year.
- 🎓 A student project: I can build and test an app without spending money on hardware, and shut everything down when I’m done.
- 🌍 A startup with global users: it can serve customers in Europe, Asia and the Middle East from nearby data centers without opening offices there.
But it’s not magic
A few things I’ve learned to keep in mind:
- You still have responsibilities. AWS secures the cloud itself, but you’re responsible for what you put in it, like who has access and how resources are configured. (This is the Shared Responsibility Model, which I’ll write about next!)
- Costs can surprise you. Pay-as-you-go also means forgetting to turn something off costs money. Setting up a budget alert is one of the first things beginners should do.
Why I think it’s worth learning
So many of the apps we use every day run on the cloud. Learning how it works feels like learning how the modern internet is built. And as a student, being able to build real things without buying hardware feels like a superpower. 🚀
Your turn: what made you curious about cloud computing? And if you already work with it, what’s one benefit you didn’t appreciate until you used it in practice? 👇
Enjoyed reading this content? Let the author know!
Your likes, comments, shares, and saves help creators reach more builders.
Loading recommendations
Loading article