Blue-green deployment
Blue-green deployment prepares a new version in a second environment. After checks, traffic switches from the current environment to the new one.
Blue-green deployment uses two comparable environments running different application versions. While the current environment serves traffic, the new one is prepared and checked. Traffic is then switched.
A hypothetical portal keeps the previous environment ready for a possible switch back. This can ease the technical transition. Whether the old version remains usable afterwards also depends on data and connected services.
If both environments share a database, a change to it may affect both. Routing traffic back does not undo that change. Newly created orders also need consideration. The strategy alone therefore guarantees neither a disruption-free switch nor complete data recovery.
Sources
Related terms
- Canary deploymentA canary deployment initially gives a new version limited traffic. Observed outcomes determine whether expansion continues or stops.
- Rolling updateA rolling update replaces running application instances gradually. Old and new versions may work simultaneously during the transition.
- 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.
- DMARC policyA DMARC policy describes the requested handling of failed domain checks. It repairs neither sending sources nor their alignment.
Articles on this topic
Cloud & Operations with ASES
Hosting, deployment, maintenance and support