• Release safety

  Rollback

  A rollback reverts a deployment to a previously known-good version when the new release misbehaves - restoring the prior artifact, container image, or routing target so users stop seeing the broken change. It is the safety net that makes frequent shipping possible: short, rehearsed, and ideally automated before it is ever needed in anger.

• Deployment strategies

  Rolling deployment

  A rolling deployment replaces old instances of an application with new ones a few at a time, so the service stays up throughout the change. Traffic shifts to healthy new instances as they come online while old ones drain - limiting downtime without provisioning the duplicate environment that blue-green requires.