WHAT
WHY
SOURCES
EXAMPLE
TOOLING
new features
toggles
users
Agile delivery
Avoid long-lived branches
Increase features integration
origin
feature
10%
90%
Progressive rollout - Early access
Canary releases - Scheduled launch
30%
70%
60%
40%
100%
0%
Dev shorcuts
mock payments
skip wizard steps
auto fill forms
Damage control - Kill switch
Permission toggles
LATAM
EUR
@a.io
@b.io
Application feature status source of truth
dev
prod
Query params
Cookies
Custom Event
Remote Flagger
Config file
Manual based
Top most priority
?featureFlags=exp_baz,dev_foo=false,ops_foo
Non authenticated context
Consistent flag behavior
featureFlags=exp_baz
Integration for external applications
Default source of truth
Feature control for team (DEVS + PO)
Log audit
Default value defined at deploy time as app config
Build (Open-source)
Pay
https://featureflags.io/ https://martinfowler.com/articles/feature-toggles.html
anthanh@etereo.io
By Anthanh
An agile way to deliver value, risk control, and manage features
I ♥ the web, technologies and....beers! Co-founder of https://etereo.io