How SRE Teams Use Canary Deployments to Reduce Blast Radius episode artwork

EPISODE · May 30, 2026 · 10 MIN

How SRE Teams Use Canary Deployments to Reduce Blast Radius

from The Site Reliability Podcast with Fexingo: SRE, Uptime, and Production Engineering · host Fexingo

In this episode of The Site Reliability Podcast, Lucas and Luna dive into the practice of canary deployments—a key strategy for reducing blast radius in production. They break down how teams like Etsy and Netflix use phased rollouts to catch issues early, with specific numbers: Etsy's Deployinator halved deployment failures after adopting canaries, and Netflix's Spinnaker pipeline automatically rolls back if error rates spike by just 1 percent. Lucas explains the optimal canary size (5-10 percent of traffic), the metrics to watch (latency, error rate, CPU usage), and why automating the rollout is critical. Luna questions whether canaries slow down velocity, and they discuss the trade-off between speed and safety. The episode also covers how to design a canary pipeline for microservices, including the use of feature flags and observability tools like Prometheus and Grafana. Recorded on May 30, 2026, this conversation gives SREs a practical guide to deploying with confidence, avoiding the all-at-once rollbacks that cause chaos. #CanaryDeployments #SRE #SiteReliabilityEngineering #BlastRadius #PhasedRollout #Etsy #Netflix #Deployinator #Spinnaker #FeatureFlags #Prometheus #Grafana #IncidentPrevention #DeploymentStrategies #DevOps #FexingoBusiness #BusinessPodcast #Technology Keep every episode free: buymeacoffee.com/fexingo

In this episode of The Site Reliability Podcast, Lucas and Luna dive into the practice of canary deployments—a key strategy for reducing blast radius in production. They break down how teams like Etsy and Netflix use phased rollouts to catch issues early, with specific numbers: Etsy's Deployinator halved deployment failures after adopting canaries, and Netflix's Spinnaker pipeline automatically rolls back if error rates spike by just 1 percent. Lucas explains the optimal canary size (5-10 percent of traffic), the metrics to watch (latency, error rate, CPU usage), and why automating the rollout is critical. Luna questions whether canaries slow down velocity, and they discuss the trade-off between speed and safety. The episode also covers how to design a canary pipeline for microservices, including the use of feature flags and observability tools like Prometheus and Grafana. Recorded on May 30, 2026, this conversation gives SREs a practical guide to deploying with confidence, avoiding the all-at-once rollbacks that cause chaos. #CanaryDeployments #SRE #SiteReliabilityEngineering #BlastRadius #PhasedRollout #Etsy #Netflix #Deployinator #Spinnaker #FeatureFlags #Prometheus #Grafana #IncidentPrevention #DeploymentStrategies #DevOps #FexingoBusiness #BusinessPodcast #Technology Keep every episode free: buymeacoffee.com/fexingo

NOW PLAYING

How SRE Teams Use Canary Deployments to Reduce Blast Radius

0:00 10:33

No transcript for this episode yet

We transcribe on demand. Request one and we'll notify you when it's ready — usually under 10 minutes.

Frequently Asked Questions

How long is this episode of The Site Reliability Podcast with Fexingo: SRE, Uptime, and Production Engineering?

This episode is 10 minutes long.

When was this The Site Reliability Podcast with Fexingo: SRE, Uptime, and Production Engineering episode published?

This episode was published on May 30, 2026.

What is this episode about?

In this episode of The Site Reliability Podcast, Lucas and Luna dive into the practice of canary deployments—a key strategy for reducing blast radius in production. They break down how teams like Etsy and Netflix use phased rollouts to catch issues...

Can I download this The Site Reliability Podcast with Fexingo: SRE, Uptime, and Production Engineering episode?

Yes, you can download this episode by clicking the download button on the episode player, or subscribe to the podcast in your preferred podcast app for automatic downloads.
URL copied to clipboard!