AWS, Azure, GCP & the future of infrastructure
≈8-12 min
"Do you use Google Drive or Dropbox? That's cloud storage! You're not storing files on your computer—they're on someone else's servers somewhere in the world."
"Think about Netflix, Instagram, Gmail... where is all that data stored? Not on your phone, right? That's the cloud."
Then ask: "What do you think 'cloud computing' actually means?"
≈10-15 min • Watch together + discuss key concepts
Let the video play through. Then discuss what stood out:
"What was the main idea? What surprised you? What didn't make sense?"
Use these questions as conversation starters (not just auto-check)
Discuss the answers out loud, or self-check first and then talk about mistakes. The buttons are optional—conversation is not.
Watch the video and answer the questions below.
≈15-20 min • Read together + discuss vocabulary & concepts
After paragraph 1: "What's the main idea? How is cloud different from traditional servers?"
After paragraph 2: "IaaS, PaaS, SaaS—explain them in your own words. Give me an example of each."
After paragraph 3: "What benefits? What challenges? Which one matters most to you?"
Cloud computing has fundamentally transformed how businesses deploy and scale applications. Instead of maintaining physical servers, companies now rent computing resources on-demand from providers like Amazon Web Services (AWS), Microsoft Azure, and Google Cloud Platform (GCP). This shift represents one of the most significant changes in enterprise technology over the past two decades.
The three main service models—Infrastructure as a Service (IaaS), Platform as a Service (PaaS), and Software as a Service (SaaS)—offer different levels of abstraction and control. IaaS provides virtualizedOne physical server pretending to be many servers. Like running Windows inside your Mac—it's virtual, not a separate computer.Example: AWS rents you "virtual servers" that are really slices of one giant machine. computing resources, PaaS offers a platform for application development, and SaaS delivers complete software applications over the internet.
Benefits of cloud computing include scalabilityYour system can handle growth automatically. When your app goes viral overnight, you don't manually buy more servers—the cloud adds them for you.Example: Like opening more checkout lanes when the supermarket gets crowded., cost efficiency, and global reach. Organizations can scale resources up or down based on demand, paying only for what they use. However, challenges remain, including security concerns, vendor lock-inWhen you're so dependent on one cloud provider (AWS, Azure, etc.) that switching becomes expensive or nearly impossible.Example: Your entire infrastructure uses AWS-specific tools—migrating to Google Cloud would require rebuilding everything., and the complexity of managing multi-cloudUsing multiple cloud providers at once (AWS + Azure + GCP). Sounds smart—no lock-in! But managing three different platforms is complicated.Example: Storage on AWS, AI on Azure, analytics on GCP. Three bills, three interfaces, three security models. environments. As serverlessYour code runs without you managing any servers. You upload code, it runs when triggered, you pay per execution—not for idle servers sitting around 24/7.Example: AWS Lambda runs your contact form code only when someone submits it. 10 submissions = 10 charges. No server running all day. computing and edge computingProcessing data closer to users instead of sending everything to a central datacenter. Reduces latency and speeds up responses.Example: Netflix stores movies on servers near you—that's why your stream doesn't buffer waiting for data from California. gain traction, the cloud landscape continues to evolve rapidly.
Ask: "Where in the text did you see this?" Then: "Why is it in that paragraph and not the others?"
Read the text above ("The Evolution of Cloud Computing"). Then, decide in which paragraph each idea is mentioned.
Choose Paragraph 1, 2, 3 — or "None of them" if not mentioned.
≈10-15 min • Apply terms in real scenarios
Answer out loud first. Then check the answer. Stuck? Go back to the reading and hover over the blue terms.
Challenge 1: "Instagram gets 10x more users overnight. Do they need 10x more servers? How does scaling work?"
Challenge 2: "1000 people hit your website at the same time. How does it not crash? Where does the traffic go?"
Challenge 3: "You want to build a contact form that sends emails. Full server or serverless? Why?"
Challenge 4: "A company uses both AWS and Azure. Why would they do that? What's the tradeoff?"
Challenge 5: "You're streaming a movie on Netflix. Why doesn't it buffer even though the servers are in California and you're in Argentina?"
≈20-30 min • Click a "?" card to reveal your speaking challenge
Pick a difficulty level. Click a card. Answer the question out loud for 2-3 minutes. Use the hints if you're stuck.
"The cloud is like a huge library where your files live on big computers somewhere else. Netflix, Google Drive—they're all stored 'in the cloud,' not on your phone. You can access them from anywhere!"
"It's like renting vs buying: owning servers costs millions upfront, needs maintenance, and can't scale fast. Cloud lets you pay monthly, scale instantly, and skip the hardware headaches."
"IaaS (AWS EC2) = raw LEGO pieces, full control. PaaS (Heroku) = half-built, just add code. SaaS (Gmail) = finished product, just use it. More control = more work!"
"With auto-scaling + load balancing, your app won't crash—it spins up more servers automatically. Costs spike, but it's better than a crashed app and lost users."
"Serverless for infrequent tasks: contact forms, image processing. You pay per execution, not 24/7. Downside: cold starts. But for 10 runs/day, why keep a server running?"
AWS: most services, huge ecosystem. Azure: best for Microsoft shops. GCP: cleaner docs, great ML. Personal? GCP. Enterprise? AWS. No "best"—just best for your use case.
For startups: waste. Too complex. For Fortune 500: insurance against vendor lock-in. But managing 3 platforms = 3× complexity, billing, security. Only worth it if downtime is unacceptable.
They complement, not replace. Edge = quick decisions (IoT, AR/VR, low latency). Cloud = deep thinking (ML training, storage). Netflix uses edge for streaming, cloud for recommendations.
Likely: runaway auto-scaling or forgotten resources. Prevention: billing alerts at $100/$500/$1000, budget limits, tag resources, audit regularly with AWS Cost Explorer.