Cloud-native architecture replaces fragile server habits with systems designed for replaceable infrastructure, distributed operation, automation, and failure. The key shift is managing state and failure deliberately instead of renting a larger version of the old server. section 9.2
Use three quick tests to expose cloud-hosting habits:
- Wipeout test: deleting a server should not delete images, sessions, or other application data stored on its local disk. section 9.2
- Midnight Patch test: fixing vulnerabilities by logging into servers manually signals configuration drift and unreproducible machines. section 9.2
- Meteor test: running everything in one Availability Zone leaves the business exposed to a single physical-site outage. section 9.2
Expensive web hosting versus cloud-ready design
An application that stores sessions on one server, receives hand-typed security fixes, and runs in one data center may use cloud hardware without being cloud-native. A cloud-ready design treats those servers as replaceable and automates recovery and management. section 9.2






