Cloud

There is a difference between learning AWS and learning cloud. The first is knowing a catalogue of services; the second is understanding concepts — elasticity, state, regions, marginal cost — that carry over to Azure or Google Cloud just the same. This category focuses on the second, with infrastructure as code as the connecting thread, because that is the practice that turns the cloud into something reproducible instead of a series of clicks nobody remembers making.

Who it is for

• Anyone about to choose a provider who does not want to decide by fashion.
• Teams already in the cloud but managing everything from the web console.
• Technical profiles who need to discuss architecture with external vendors.

What you will learn

• Service models and which responsibility remains yours in each.
• Infrastructure as code with Terraform, and why state matters so much.
• Serverless architectures and when they get expensive.
• High availability and regions, without over-engineering from day one.

Recommended order

1. Provider-agnostic cloud concepts first, even if your provider is decided.
2. Then one specific provider in depth, usually AWS.
3. Infrastructure as code at the end, once you know what you are describing.