Skip to content

Deployments

JayBeeDe edited this page Jan 6, 2024 · 1 revision

Rolling Deployments

Everything at the same time

✅ good for vendor-packaged solutions like desktop applications ✅ good for non-production systems (e.g., re-creating a development environment) ❌ bad for modern applications since risks are unacceptable

Rolling Deployment

✅ good since no downtime ✅ sometimes coexistence is difficult / not compatible ✅ Good for distributed systems, suitable for containers

Blue-Green, Red-Black or A/B Deployment

A/B Deployment

A/B Deployment

Fail-safe process

✅ Rollback easy

❌ Relies on traffic routing, DNS CNAMES can takes long due to long TTL ❌ Requires 2 identical environment

Canary Deployment

Like blue-green, deploys to small group of users:

  • Geographic area
  • IP address
  • Internal / External users
  • For defined user groups

❌ + Risky

Canary Deployment

Sources

https://dev.to/mostlyjason/intro-to-deployment-strategies-blue- green-canary-and-more-3a3

Clone this wiki locally