Zero downtime
Zero downtime is the condition in which a service remains available without interruption during a change or operational activity.
Elasticsearch in Action, Second Edition
Zero downtime is continuous service availability during an operational change without application interruption.
- How it is used
- Supports uninterrupted Elasticsearch reindexing and migration by routing application operations through a stable alias.
- How deep it goes
- Explains alias creation, multi-index write selection, inspection, and coordinated removal and addition, without detailing reindexing procedures.
- Examples
- Uses cars_for_aliases, vintage_cars, vintage_cars_new, and multi-index car aliases to demonstrate routing and migration.
- What you can do after
- Operate/configure Elasticsearch aliases to redirect searches and writes during an index migration.
Read how Elasticsearch in Action, Second Edition explains zero downtime →
Platform Engineering on Kubernetes
Zero downtime is an operational condition in which a service remains available while software changes are applied.
- How it is used
- Supports continuous delivery by keeping applications available while Kubernetes components are updated.
- How deep it goes
- Explains the operational rationale and dependencies but defers detailed release strategies to later treatment.
- Examples
- Uses a Kubernetes cluster, Helm packaging, YAML resources, and independently updated application services.
- What you can do after
- Operate Kubernetes-based releases that update application components without stopping the entire application.
Read how Platform Engineering on Kubernetes explains zero downtime →
Kubernetes for Developers
A zero downtime update is an application update performed without interrupting service availability to users.
- How it is used
- Preserves service availability while Kubernetes updates application Pods.
- How deep it goes
- Explains readiness gating, rolling-update sequencing, coexistence, and tuning, but defers advanced blue/green implementation.
- Examples
- Uses a three-replica timeserver, HTTP checks, curl monitoring, and configurable maxSurge and maxUnavailable values.
- What you can do after
- Operate/configure Kubernetes Deployments for traffic-safe rollouts using readiness probes and RollingUpdate settings.
Related concepts
- aliasaddressed by · An alias is an alternative name by which an entity, command, parameter, or resource can be referred to.
- Kubernetesproduced by · Kubernetes is an open-source platform for orchestrating and automating the deployment, scaling, and management of containerized workloads across computing clusters.
- readiness checkproduced by · A readiness check is a health probe that determines whether a running service or workload is prepared to receive requests or traffic.
- maximum tolerable downtimecontrasts with · Maximum tolerable downtime is the longest period an organization can tolerate a service or business function being unavailable before unacceptable consequences arise.
- queueaddressed by · A queue is an ordered collection that holds items for retrieval or processing, typically removing them in the order they were added.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.