| user id(s) | geo | time | …. (Stored in config-file | database | env-var | in the code | FTaaS) Toggle Context = env | user id(s) | geo | time | logged-in-state | tenant-id | … Toggle Router = reads the toggle configuration + context to determine which toggle point to activate Toggle Point = execution path(s) for the toggle state(s)
the context of Continuous Integration (CI) Allow for large feature branches to be merged in master Long lived (based on how long the feature branches take - weeks? months?)
Almost exclusively used in Production Short lived (days) till a baseline is established Can be lifetime (kill switches!) Help with graceful degradation
of users May need to evaluate the user authorizations Canary, or incremental rollouts Beta, Early Adopters (or Early Winners as we call ‘em!) Can be very short (hours) or long (lifetime) lived
flags go bad - Edith Harbaugh : https://www.youtube.com/watch?v=28ZAoStv-Xw Getting Started with Feature Flags - #1 LaunchDarkly Feature Flags : https://www.youtube.com/watch?v=pwA_Ehp2SMY