Reducing Release Risk with Feature Flag Management
summary
Company replaces risky deploys with feature flags using Harness to serve multi-variant frontend experiments on a jQuery kiosk view and to avoid blue‑green downtime during DB migrations. Implementation takes a few hundred lines of code, integrates with existing CI/CD, and toggles features for small customer cohorts so failures stay isolated. Production rollout happens this month, change‑failure tolerance drops to ~0, and product teams flip flags without engineering releases. Harness few hundred lines of code kiosk view
AI-written summary · about
chapters (7)
- 0:00Introduction
- 1:46Metricus and products
- 6:26Release risk problem
- 8:53Feature flags solution
- 10:41Why Harness was chosen for feature flagging
- 12:48Harness implementation results
- 13:54Summary
related talks
59mFaster & less risky releases with feature flags
41mFeature Flags: Separate Deployment from Feature Release
44mFlagging features — a DevOps approach to continuous release
30mChoose Your Own Deployment: Interactive Feature Flag Adventure
50mThe Story of One Feature Flag
08mThe Art of Feature Flagging
07mKeep Calm and Deploy On: Creating Safer Releases with Feature Flags
42mDeploy often, stress less: feature flags in production