Cloud architecture is more than moving an application to a rented server. It changes how you treat hardware: servers become temporary and disposable, while Infrastructure as Code (IaC) makes environments repeatable through version-controlled files. section 9.1.2
Use three checks to spot fragile habits:
- Wipeout: Would deleting a server lose data stored on its local disk? section 9.2
- Midnight Patch: Do you log in and manually fix security vulnerabilities? section 9.2
- Meteor: Would an outage in one Availability Zone take the whole application offline? section 9.2
Cloud compute choices trade control for convenience. An EC2 instance, Docker container, Kubernetes cluster, Azure Function, or AWS Lambda sits somewhere on that spectrum; more control also means more maintenance. section 9.4
A practical first step
Deploy a simple web app—even a “Hello, World” API—with IaC. Put the setup in version control and peer review, rather than relying on one-off manual configuration. section 9.1.2
Figure 9.2 The Compute Spectrum: You are always trading the power to control the environment for the speed of convenience.

Compare the control and convenience ends of the compute spectrum. section 9.4
