11 June 2026
Why Blue/Green and Canary deployments aren't competing strategies: Canary handles gradual feature rollout behind flags, while Blue/Green provides the instant, clean rollback that Canary alone can't guarantee against hidden side effects.
Tagged “blue-green-deployment”
← All articles20 May 2026
How blue/green deployment in Azure Container Apps and feature-flag-driven canary rollout in Azure App Configuration work together on a real demo: stable blue serving production traffic, green tested separately, with per-user feature flags controlling which AI features (sentiment, language detection, summarization) are live.
19 May 2026
Building the blue/green + feature-flag demo for AZ-400 practice: adding a user header, moving a feature from an env variable to an App Configuration flag — and the real debugging story, a 502 traced to GitHub Actions mangling a multi-line prompt.
2 May 2026
A 60-second canary deployment demo: traffic split at the ingress controller between blue and green environments, plus a sticky-session example, all served over a real HTTPS production URL.
2 May 2026
Week 3 of an AZ-400 side project: a full Terraform + AKS + Traefik pipeline covering infrastructure, blue/green + canary deployment, and teardown — with real execution times for each stage, down to seconds for a blue/green traffic switch.
26 April 2026
The first working blue-green deployment on AKS for AZ-400 practice: three pipelines split across infrastructure provisioning, deployment, and Traefik IngressRoute-based promotion between two Git-branch environments.
25 April 2026
Adding a detect-language endpoint to the sentiment API, backed by AI-assisted unit tests (Aider + Qwen) that also run on main, a feature-branch flow set up for blue-green then canary, and a Flask route-ordering gotcha (routes must be defined before the blocking app.run() call).