All 16 CI/CD, Publishing & Deployment questions
More in CI/CD, Publishing & Deployment
How do feature flags decouple code deployment from feature release in a CI/CD workflow? What is the difference between dotnet publish's --self-contained and framework-dependent options in the context of container image builds? What is the difference between blue-green deployment and canary deployment, and how do they apply to .NET applications? How do you set up automated database migrations as part of a .NET CI/CD deployment pipeline safely? How does GitOps (e.g., using Flux or ArgoCD with Kubernetes) change the deployment model compared to traditional push-based CI/CD pipelines? What is the purpose of a multi-stage Dockerfile for .NET applications, and how does it reduce final image size? How do you implement automated rollback in a CI/CD pipeline triggered by post-deployment monitoring signals (error rate, latency)? What is Native AOT compilation in .NET, and what are its main benefits and limitations?
Advertisement
.NET › CI/CD, Publishing & Deployment

How does deployment slot swapping (e.g., Azure App Service deployment slots) enable near-zero-downtime deployments?

Advanced

Answer

Deployment slots let you deploy a new version to a separate, fully warmed-up staging slot (with its own URL for testing) and then perform an atomic swap that exchanges the staging and production slot's routing, making the new version live instantly with the previously-production version now sitting in staging (as an instant rollback target) -- avoiding the cold-start delay and brief unavailability of a traditional stop-deploy-start deployment.
az webapp deployment slot create --name myapp --resource-group myapp-rg --slot staging
az webapp deployment source config-zip --resource-group myapp-rg --name myapp --slot staging --src ./publish.zip
# After verifying staging slot works correctly:
az webapp deployment slot swap --resource-group myapp-rg --name myapp --slot staging --target-slot production
Real-world example An e-commerce site deploys a new version to a staging slot, runs automated smoke tests against its dedicated URL, and only then swaps it into production, keeping the previous version instantly available in the staging slot for immediate rollback if any issue is discovered post-swap.

Common follow-ups: What happens to in-flight requests during a slot swap?;How do slot-specific app settings (like connection strings) avoid being swapped along with the code?

Docker & Containerization;Health Checks & Readiness/Liveness Probes
All 16 CI/CD, Publishing & Deployment questions