Cloud Concepts overview
85 topics in 11 lessons, each in one line. Every topic opens the page that teaches it.
After this course you can
- Explain what cloud computing is, why it is cheaper and faster than owning hardware, and where it is not.
- Choose between compute, storage, database and network building blocks for a given need, on any provider.
- Read a cloud bill, a shared responsibility question and an availability design the way the exams expect.
1What the cloud is
- What the cloud isThe cloud is a data centre you rent over the internet
- Owning serversOwning means buying for the peak and paying for the idle
- ElasticityRenting follows demand: capacity rises and falls with the load
- Capital and operating expenseA purchase becomes a bill: capital expense turns into operating expense
- AgilityMinutes, not months: a new server is one request away
- When the cloud costs moreRenting wins when demand moves; a flat load can be cheaper to own
- The providersThree providers hold about 63% of the market
2Service models and shared responsibility
- The stackEvery application sits on the same nine layers
- Service modelsA service model is a line through the stack: above it is yours
- IaaS: infrastructure as a serviceRent the machine, run everything on it
- PaaS: platform as a serviceBring the code, the platform runs it
- SaaS: software as a serviceFinished software, you just use it
- Control and convenienceMore done for you means less you can change
- Shared responsibilityThe provider secures the cloud; you secure what you put in it
- Shared responsibility by modelThe line moves with the service model; three rows never do
- What is always yoursYour data, your identities and your devices are always yours
- ComplianceA certified cloud certifies the floor, not what you build on it
- Choosing a service modelTake the most managed option that fits
3Regions, zones and the edge
- RegionsThe cloud is in real places: a region is a location you choose
- Availability zonesA region is three or more zones; a zone is one or more data centres
- Why zones existZones exist so that one failure cannot take everything
- LatencyDistance is delay: about 1 ms for every 100 km, there and back
- Choosing a regionFour questions pick a region: law, distance, services, price
- Resource scopeEvery resource has a scope: a zone, a region, or the world
- Edge locationsHundreds of small sites bring content close to users
- Data residencyRegions are isolated: nothing leaves one unless you send it
4Compute
- ComputeFour ways to run code, from a whole machine to a single function
- Virtual machinesA virtual machine is a slice of a physical server
- AutoscalingA group of identical machines that grows and shrinks
- ContainersA container packs the app with what it needs and shares the OS
- Container orchestrationAn orchestrator keeps your containers running across many machines
- Serverless functionsA function runs only when something happens, and bills by the millisecond
- Platform as a serviceA platform turns “here is my code” into a running website
- Choosing computeTake the least you have to manage
5Storage
- StorageThree kinds of storage for three ways of reaching data
- Object storageWhole files under names, with no limit on how many
- Durability and availabilityEleven nines: every object is copied across three zones
- Storage classesPay less to store, and more to read
- Block storageA disk attached to one machine
- File storageOne folder tree, mounted by many machines at once
- Choosing storageHow the data is reached decides, and the price agrees
- Data transferMoving a mountain of data: sometimes a lorry beats the wire
6Networking
- Virtual networksYour own private address space in the cloud
- Public and private subnetsA route to the internet decides what can be reached from outside
- Security groupsEvery port is closed until a rule opens it
- Load balancersOne address in front of many servers
- DNSThe name decides where the user lands
- Connecting your own buildingTwo ways in: a VPN over the internet, or a dedicated line
- The whole pathOne request passes six steps, and only one faces the internet
7Databases and data services
- Managed databasesThe provider does the chores; you keep the tables and queries
- Relational databasesTables that refer to each other
- NoSQL databasesFind anything by its key, at any size
- Data warehousesBuilt for questions about everything
- CachesKeep the answer you already worked out
- QueuesHand work over without waiting for it
- Choosing a data serviceOne application, six kinds of data
8Identity and access
- Identity and access managementEvery request is checked twice: who are you, and may you do this?
- Users, groups and rolesPermissions attach to groups and roles, not to one person at a time
- PoliciesA policy says who may do what, to which resources, and when
- Least privilegeGrant only what the job needs, and a stolen key can do only that
- Multi-factor authenticationA stolen password opens nothing when a second proof is required
- Identities for softwareSoftware gets a temporary pass from a role, never a key stored in code
- Accounts and organisationsSeparate accounts are the strongest wall, under one set of rules
9Cost
- The cloud billEvery bill is three meters: time switched on, space used, data sent out
- Pricing modelsOne server, three prices: full, committed, or spare capacity
- Idle resourcesYou pay for what is switched on, so switch off what nobody is using
- Budgets and alertsA budget warns you during the month, not on the invoice
- TagsA label on every resource turns one bill into a bill per team
- Total cost of ownershipCompare everything owning costs, not the price of a server
- Managing costCost is managed in a loop: see it, cut it, keep watching
10Availability, monitoring and support
- AvailabilityAvailability is counted in nines, and each nine is ten times harder
- High availabilityNo single point of failure: two of everything, kept apart
- Disaster recoveryTwo numbers define a recovery plan: data lost, and time down
- MonitoringYou cannot fix what you cannot see: metrics, logs and traces
- Infrastructure as codeDescribe the system in a file, and it can be rebuilt identically
- Support plansSupport is a paid plan: you buy how fast an engineer answers
- Well-architected designSix questions judge any design, and you can now answer them
11Moving a booking app to the cloudWorked case
- The problemA move to the cloud is a design decision, not a copy
- The estimateSize from the numbers, not from the old hardware
- Lift and shiftLift and shift: the same machines, rented by the hour
- The causeLift and shift moved the rack, with every weakness of the rack
- The redesignTwo zones and managed parts meet the target, and cost more
- The trade-offPay for what the target needs, then commit to the floor
- The designThe same design on every provider; only the names change
- A real caseNetflix rebuilt for the cloud rather than copying
Sources and credit
79 sourcesThe chapters and drawings are written by NeuroqAI from these sources. Each lesson lists its own at the end of its chapter, and figures on the pages are taken from them or computed from them.