More Deployment Strategies — Development Strategies
Beyond Blue-Green and Canary, several other deployment patterns exist for different scenarios and risk profiles. Rolling (Incremental) Deployment Rolling gradually replaces servers one-by-one (or in batches), replacing old version with new while keeping service running. Process: You have 10 servers running v1 Stop server 1, deploy v2, restart it Remove from load balancer during deployment Once healthy, add back to load balancer Repeat for servers 2-10 Advantages: Minimal extra infrastructure — no need for full duplicate environment Gradual process — if issues arise, fewer users affected Cost efficient — don't need double resources Disadvantages: Longer deployment time — takes time to update all servers Version mixing — old and new versions run simultaneously (can cause compatibility…
Key Takeaways
Rolling: update servers one-at-a-time, cost-efficient but slower.
Shadow: duplicate traffic to new version, validate risk-free.
A/B Testing: measure which version is better with real users.
Recreate: stop all, deploy all, start all (avoid in production).
No single strategy is best — combine for your use case.
Monitor, feature flags, and easy rollback are essential for all strategies.