liveBook · Manning

Uptime

As explained in Effective Platform Engineering

High availability is the design of a system to maintain service access despite component failures or maintenance.

High availability (HA) keeps services accessible through redundancy and the redirection of traffic to healthy infrastructure. It concerns uptime; resilience is distinct, describing a system’s ability to self-correct after failure. section 1.3.3 section 8.3

Apply HA with production confidence and developer access in mind:

  • Test HA and resilience configurations outside production; skipping HA there can undermine confidence in releases. section 8.3
  • Balance nonproduction costs against the time developers lose when blocked and the delays to revenue-generating features. section 8.3

Platform services pipeline

Epetech’s demo configurations omit full HA options for services such as metrics-server, kube-state-metrics, and event-exporter. That simplification is for demonstration; production environments should enable HA. section 8.3

How Effective Platform Engineering covers it

How deep it goes
Distinguishes availability from self-correcting resilience and recommends nonproduction testing, without detailing HA configurations.
Examples
Uses demo configurations for metrics-server, kube-state-metrics, and event-exporter to contrast nonproduction and production HA.
What you can do after
Evaluate the cost of omitting nonproduction HA against developer blockage and reduced release confidence.
How it connects
Connects high availability with resilience, release pipelines, and service availability metrics.

Also explained in

Compare how 20 books explain uptime →

Related concepts

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