The whole map

19 chapters · 150 topics · 9,555 slides

Home
01What the cloud actually isFoundations
01Why this is worth learning02How renting computers became normal03What "the cloud" actually means04How one computer reaches another05The machines, and the buildings they live in06Where in the world your machine sits07How much of the work you hand over08Whose building is it09Who is to blame when it breaks10Buying versus renting, in money11Who you can actually rent from12Five things people believe that are not true
02How a visitor finds youGetting connected
13What a cloud network is made of14How machines are numbered15Turning a name into a number16The language browsers and servers speak17The padlock, and what it actually proves18Sharing the visitors between machines19Keeping copies close to your visitors20The thing in front of the thing21Your own private area inside a public cloud22Joining the cloud to a building23Running code near the visitor24The company that ended up in front of everything
03The machines that run your codeRenting machines
25How one machine becomes forty26Choosing what to rent27Letting the number of machines change by itself36Choosing what kind of thing runs your code
04Software that runs the same everywherePacking it up
28Sealing software into a package29Where the packages are kept30Running hundreds of packages without a person31The parts that make it hard32Letting somebody else run it
05Code with no machine to look afterPaying for nothing
33Code that exists only while it runs34The middle option35Handing over a folder of code
06Designing something that holdsPutting it together
37One program that does everything38Several programs instead of one39Telling the world something happened40The waiting room between programs41How programs agree to talk46The four questions professionals ask of any design
07Surviving the day everyone arrivesUnder pressure
42Having the answer ready before the question43Growing bigger, or growing wider44Surviving a failure without anybody noticing45When a whole building goes
08Where the information livesKeeping things
47The three shapes information is kept in48The store everything ends up in55Keeping information for asking questions of56Moving information from where it is to where it is useful57Copies for the bad day58Where information is legally allowed to be
09Asking questions of your informationAnswers, fast
49What makes this different from a folder50Facts in tables51The other family52Letting the provider run it53The store that lives in memory54Finding things by meaning
10Keeping it all lockedLocks and keys
59The way to think about all of this60Who is allowed to do what61Who your visitors are62Where the passwords live63Making information unreadable64Attacks aimed at the front door65The rules you are legally required to follow66Noticing, and what to do at three in the morning67Checking the work automatically68Assuming the walls have already failed69The list to run on every client70What actually went wrong, in real cases
11Changing it without fearRunning it daily
71The idea underneath all the tools72Keeping every version of everything73Letting a machine do the releasing74The one most people use75The alternatives76Writing down the infrastructure77The tool most people use for that78The alternatives to that tool79Setting up what is inside the machines80Making the written-down version the truth81Finding out something is wrong before the client does82What to actually use for that83Deciding how reliable is reliable enough84Making the easy path the correct path85When it breaks at three in the morning
12Amazon Web ServicesThe three big companies
86The shape of the biggest one87The twelve services that do most of the work88The rest of the catalogue89How the bill is put together
13Microsoft AzureThe three big companies
90The cloud built around a company's staff list91The services you will actually use
14Google CloudThe three big companies
92The cloud built by a company that had to invent scale93The services you will actually use
15The smaller, faster cloudsThe alternatives
94The cheaper, simpler clouds95Hosting a site from a folder of code96A ready-made back end, built on ordinary parts97The other ready-made back end98The middle tier99Choosing between all of them100Depending on one company
16The bill, and how to bend itMoney
101The ways renting is charged for102Managing cost as an ongoing practice103Estimating before you build104Where the money actually leaks105When the answer is to stop renting
17Twelve systems, fully drawnWorked examples
106How to read any of these107A restaurant that takes orders108An online shop109Software sold by subscription110A hospital system111Customer records112Company resource planning113A school platform114A banking application115Live chat116A marketplace117A booking system118An application built around a language model
18Selling cloud, not hoursThe business
119The size of the thing you are entering120What agencies actually sell121Turning what you do into something with a price122How to charge123What people actually charge124Working out what something will take125Being paid every month126The conversation before the work127Writing it down128The legal parts129Where the work comes from130The providers' partner programmes131Selling through the providers' own shops132Choosing what you are for133Knowing who else is in the room134Being found135Delivering the same way every time136Who does the work137The numbers of the business itself138When it goes wrong
19The twelve-month pathYou, next year
139The shape of twelve months140The first four weeks141Months two and three142Months four to six143Months seven to twelve144Which certificates are worth it145What to show people146The questions you will be asked147The things to actually build148Every word, in one place149Where all of this came from150From building websites to running systems