Rolling update
A rolling update replaces running application instances gradually. Old and new versions may work simultaneously during the transition.
A rolling update gradually replaces running application instances with a new version. Old and new instances can handle requests at the same time during the transition.
A hypothetical portal first replaces part of its instances and continues after planned checks. This requires sufficient capacity and suitable readiness checks. New instances should not count as usable merely because their processes have started.
Both versions must also work with shared data and interfaces. An incompatible database change can violate this prerequisite. Gradual replacement therefore guarantees neither successful orders nor automatic recovery. A limited canary check can complement it; its emphasis differs from instance replacement.
Sources
Related terms
- Blue-green deploymentBlue-green deployment prepares a new version in a second environment. After checks, traffic switches from the current environment to the new one.
- Canary deploymentA canary deployment initially gives a new version limited traffic. Observed outcomes determine whether expansion continues or stops.
- KubernetesKubernetes manages containerised applications against a declared desired state. Its value also depends on configuration and operational responsibilities.
- Return-PathReturn-Path records the SMTP reverse path in a header. It explains the technical route for error reports, not a person’s identity.
- Envelope-FromEnvelope-From identifies the SMTP sender for transport and error feedback. It must be distinguished from the visible sender address.
- DMARC aggregate reportA DMARC aggregate report summarises a reporting mail system’s domain checks over a period. It helps examine sending sources and misconfigurations.
Articles on this topic
Cloud & Operations with ASES
Hosting, deployment, maintenance and support