Cost a workload
Work out what a small web shop costs to run on its own servers and in the cloud, over three years, in a spreadsheet.
Open the project: Cost a workloadWhat the cloud is, why companies moved to it, and the ideas every provider shares: service models, regions and zones, scaling, paying for use, and who is responsible for what.
Beginner · 10 topics · 2 projects · about 1 hour of reading
Step 8 of the DevOps engineer roadmap
Renting computers instead of buying them, and the five things that make a service a cloud.
Buying and running your own servers, what that cost, and why most companies stopped.
Data centres, virtual machines, and the APIs that let you create a server in a minute.
IaaS, PaaS, SaaS and serverless, and what you manage in each.
Public, private, hybrid and multi-cloud, and why a company picks one.
Where the computers actually are, and how regions and availability zones keep a service running when a building fails.
Bigger machines or more machines, scaling down as well as up, and designing for machines that fail.
Pay-as-you-go, reserved and spot prices, the costs people forget, and how bills surprise teams.
What the provider secures, what you secure, and how that line moves with the service model.
AWS, Azure, Google Cloud and the rest: the same ideas under different names.
Do these after the topics. Each one runs on your own computer.
Work out what a small web shop costs to run on its own servers and in the cloud, over three years, in a spreadsheet.
Open the project: Cost a workloadTake a company's servers and write a one-page plan: what moves, which service model, how many zones, and who secures what.
Open the project: Plan a move to the cloud