What is the Cloud?
The cloud is other people's computers, rented by the second. Here is what that actually means for building software and why it changed everything.

Why the cloud changed everything
Before cloud computing (roughly pre-2006), running a web app required:
- Buying physical servers (thousands to tens of thousands of euros)
- Renting space in a data centre (colocated hosting)
- Managing hardware: replacing failed disks, maintaining cooling
- Guessing the right capacity upfront, too little and your site crashes under load; too much and you waste money
Amazon Web Services launched in 2006. More: History of cloud computing, Wikipedia
The cloud eliminated all of this. You rent computing capacity by the hour or second. If your app goes viral and needs 100x more capacity, you provision it in minutes. If you shut down the project, you turn off the resources and stop paying. No hardware, no long-term contracts, no upfront capital cost.
The three major cloud providers
AWS (Amazon Web Services), launched 2006, largest market share (~33%), broadest range of services (200+). The default choice if you have no strong reason to pick otherwise.
Microsoft Azure, strong in enterprise (especially Microsoft ecosystem: Active Directory, .NET, Windows Server). Second-largest provider.
Google Cloud Platform (GCP), strong in AI/ML, big data (BigQuery), and Kubernetes (they created it). Growing market share.
All three offer similar core capabilities. The choice typically comes down to what your team knows, what tools you are using, or compliance requirements. Free tiers on all three let you experiment at no cost.
IaaS, PaaS, and SaaS, the cloud service model
The cloud is not one thing. It is a spectrum of how much the provider manages:
IaaS (Infrastructure as a Service), you rent raw resources: virtual machines, storage, networking. You manage the operating system, runtime, security updates, and application. Maximum control, maximum responsibility. Example: AWS EC2, Google Compute Engine, DigitalOcean Droplets.
PaaS (Platform as a Service), you deploy code; the provider manages the underlying infrastructure, OS, and runtime. You focus on your application. Less control, far less management overhead. Example: Heroku, Railway, Render, Google App Engine.
SaaS (Software as a Service), you use finished software through a browser. No infrastructure to manage. Example: GitHub, Notion, Salesforce, Google Workspace.
For building your first app: PaaS is the right starting point. Push code from GitHub, the platform deploys it. No server management.
What cloud services actually include
“The cloud” covers thousands of individual services. The most commonly used categories:
| Category | What it provides | Examples |
|---|---|---|
| Compute | Run code (VMs, containers, functions) | EC2, Lambda, Cloud Run |
| Storage | Store files and large binary data | S3, GCS, Cloudflare R2 |
| Databases | Managed relational and NoSQL databases | RDS (PostgreSQL), DynamoDB, Firestore |
| Networking | Load balancers, CDNs, DNS, firewalls | CloudFront, Cloud CDN |
| AI/ML | Pre-trained models, GPU instances, AI APIs | Bedrock, Vertex AI |
| Security | Identity management, secrets, certificates | IAM, KMS, Certificate Manager |
| Monitoring | Logs, metrics, alerts | CloudWatch, Cloud Logging |
| Email/SMS | Transactional messaging | SES, Twilio (not strictly cloud but partner) |
A simple web app typically uses compute (to run the code) + storage (for files) + a managed database. You do not need to understand everything.
CDN: making your app fast for everyone
A CDN (Content Delivery Network) stores copies of your static assets (images, CSS, JavaScript, videos) on servers distributed around the world. When a user in Tokyo requests a file from a server in Frankfurt, it is slow. When they request it from a CDN edge server in Tokyo, it is fast.
CDNs like Cloudflare , AWS CloudFront, and Fastly are used by virtually every production website. They also provide DDoS protection and reduce the load on your origin server. More: What is a CDN?, Cloudflare
Regions and availability zones, where data lives
Cloud providers split their infrastructure into regions (geographic areas) and availability zones (separate data centres within a region). Examples:
eu-west-1= AWS Irelandeurope-west1= GCP Belgiumus-east-1= AWS Northern Virginia
This matters for two reasons:
- Latency, running your app in the same region as your users makes it faster. A server in Ireland is faster for European users than one in Virginia.
- Data sovereignty, GDPR and similar regulations may require that data about EU residents stays in EU-based servers. Choose your region accordingly.
Multi-region deployment (running in multiple regions simultaneously) makes your app resilient to a single data centre failure and reduces latency globally. Most production apps start in one region and expand later.
Cloud costs, what to expect
Cloud billing is based on usage. Common cost drivers:
- Compute: per vCPU per hour and GB RAM per hour
- Storage: per GB per month
- Data transfer: usually free to receive (ingress), charged to send (egress)
- Database: instance size per hour plus storage
For a prototype or small app: free tiers cover most of what you need. AWS Free Tier, GCP Free Tier, and Azure Free Account all provide 12 months of meaningful free resources for new accounts.
For production apps: start small and monitor. Tools like Infracost estimate costs from your infrastructure code before you deploy.
Recommended starting points
| You want to… | Use |
|---|---|
| Deploy a React/Next.js app | Vercel , push to GitHub, deployed instantly |
| Deploy any backend service | Railway or Render |
| Store files and images | Cloudflare R2 or AWS S3 |
| Managed PostgreSQL | Supabase or Neon |
| Learn proper cloud (AWS) | AWS Free Tier |
Further reading
- What is cloud computing?, AWS
- Cloudflare Learning Center , excellent free articles on CDNs, networking, security
- Google Cloud skills boost (free) , hands-on labs
- AWS Skill Builder (free tier) , structured AWS learning paths
- The Twelve-Factor App , methodology for cloud-native application design
- ByteByteGo on YouTube , system design and infrastructure diagrams
What’s next
Next: What is an API? , how different pieces of software talk to each other, and how your app connects to external services.
Frequently asked questions
