1. 1.The act of storing a computed response close to the user so that the next request avoids the origin entirely.
2. 2.A negotiated agreement between freshness and speed, usually governed by a tag or TTL.

“Tagged caching let the marketing page serve in under ten milliseconds worldwide.”

1. 1.The controlled promotion of an immutable build artifact from source to production traffic.
2. 2.A moment of trust between the team shipping code and the users receiving it.

“A green deployment is one that nobody on call ever has to think about.”

1. 1.The transformation of data into ciphertext so that only the intended recipient can recover it.
2. 2.A default, not a feature — applied at rest, in transit, and in backup without asking.

“End-to-end encryption makes the engineer on call as blind as the attacker.”

1. 1.The automatic routing of traffic away from an unhealthy region toward a healthy one.
2. 2.A rehearsal the platform runs in production every single day.

“The us-east failover finished before the first Slack message landed.”

1. 1.The property of a system that lets engineers answer questions they did not think to ask at build time.
2. 2.Logs, metrics, and traces stitched together around a shared request id.

“Good observability turns a midnight page into a five-minute fix.”

1. 1.The act of adding capacity in response to demand, ideally before the user notices.
2. 2.A quiet art in which the best result is that nothing interesting happened.

“Autoscaling absorbed the Black Friday spike without a single deploy.”