Deployment Strategies
Nife supports multiple deployment strategies to minimise risk and downtime when releasing new versions.
Available Strategies
Rolling Deployment
Gradually replaces old instances with new ones. Zero downtime, but both versions run simultaneously during the update.
Blue-Green Deployment
Maintains two identical environments (blue = current, green = new). Switch traffic instantly once the new version is verified.
Benefits:
- Instant rollback by switching back to blue
- No downtime during deployment
- Full testing of new version before going live
Canary Deployment
Routes a small percentage of traffic to the new version first. Gradually increase traffic as confidence grows.
Benefits:
- Reduced blast radius if new version has issues
- Real user testing before full rollout
- Easy rollback
A/B Testing
Runs two variants — Variant A (Control) and Variant B (Test) — side by side on a configurable traffic split. Real users are tracked on each variant so you can compare views and conversions directly, instead of guessing which version performs better.
Benefits:
- Evidence-based decisions, backed by real conversion data instead of a guess
- Both variants keep running as long as you need, with traffic reweighted at any time
- Built-in statistical significance check before you're allowed to declare a winner
For the full walkthrough — traffic split, conversion tracking, results, and declaring a winner — see A/B Testing.
Configuring Strategies
- Navigate to your application in the Nife dashboard
- Go to Deploys → Strategies
- Select your preferred strategy
- Configure traffic split percentages (for canary)
- Deploy