Keep Calm and Deploy On: Creating Safer Releases with Feature Flags
summary
Argues that feature flags go beyond booleans to JSON flags and numeric/string controls, and that long‑lived “safety valve” flags let systems degrade noncritical parts and pivot to a fallback service instead of failing. Claims rollback and protection of uptime can happen in about 200 milliseconds, bad actors can be isolated by returning a 404 for that one bad acting device, and fixes are validated via audit log and observability while staged rollouts (subset → wider) and live config tuning by IP or node minimize risk.
AI-written summary · about
related talks
59mFaster & less risky releases with feature flags
40mWhen Feature flags go bad
53mDr Sheldon Cooper Presents: Fun with Flags
41mFeature Flags: Separate Deployment from Feature Release
56mWhen Feature flags go bad
42mDeploy often, stress less: feature flags in production
08mThe Art of Feature Flagging
44mFlagging features — a DevOps approach to continuous release