liveBook · Manning

Cloud-native architecture

As explained in Grokking Software Architecture

Cloud-native architecture is an architectural approach that treats infrastructure as replaceable and designs explicitly for distributed operation, automated management, and failure.

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

How Grokking Software Architecture covers it

How deep it goes
Defines three failure-oriented diagnostic tests but stops short of implementation patterns for achieving cloud readiness.
Examples
Uses lost local data, manual vulnerability fixes, and single-site outages as concrete diagnostic scenarios.
What you can do after
Diagnose fragile cloud deployments and identify state, patching, and single-location failure risks.
How it connects
Connects state management, failure handling, configuration drift, and Availability Zones.

Also explained in

Compare how 7 books explain cloud-native architecture →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Grokking Software Architecture. The section links point to the parts of the book it draws on.