Cloud Computing
7 clusters, spanning half-life layers 1–3: Major providers, Developer clouds & PaaS, AWS essentials, Azure essentials, GCP essentials, Service models, Core concepts.
Clusters
Section titled “Clusters”Major providers
The primitive set maps near 1:1, which is what makes the second cloud cheap and the first expensive. IAM is where the mapping breaks worst —…
Developer clouds & PaaS
The build → deploy → edge shape transfers across all of them. Runtime constraints differ sharply: Workers is not Node, and code written for one edge…
AWS essentials
Sub-entities of AWS, listed because each is a package in its own right. IAM is the one that gates everything else and should come first.
Azure essentials
Same shape as AWS’s list. Entra ID is the IAM analogue and the same “learn it first” argument applies.
GCP essentials
Cloud Run is the most transferable member — it is the clearest container-to-URL primitive on any cloud.
Service models
Where the responsibility boundary sits is the durable content, and it transfers to every provider and every on-prem argument.
Core concepts
Failure domains, elasticity and the shared-responsibility model transfer to every provider and outlive their service names.