For the development team to manage release process instead of source control branches. Should be short lived and thus removed to keep technical debt low.
Business Feature Toggles
For the benefit of the business such that they tailor the user experience based on business requirements. Consider a regular edition vs pro edition of software. Typically long lived or forever.
Configuration Types
Compiled ConfigurationToggle value baked-in to assembly.
Features can only be enabled or disabled with new release
Multiple machines may need to be kept in sync
Local Configuration
Toggle values held in app/web.config
Can be changed without needing an new release
Multiple machines may need to be kept in sync
Centralized Configuration
Toggle values held in central location, database, network share, UI, etc.
Can be changed without needing a new release
Whole system can be managed centrally
Business can manage potentially via UI.
Toggle decision points
User interface element toggling
Toggle links to new page / screen
Number of decision points
Defaults
Don't set defaults for toggles. An exception should be thrown if state of toggle is unknown.
Alternatives to release toggles
Deliver smaller part of features (small releases and more often)
Build the backend first and then build user interface last. Delays testing of UI to end of cycle.
Suggested Open Source Solutions
FeatureToggle - Popular choice, actively developed, nice choice.
FeatureSwitch
FeatureSwitcher
No comments:
Post a Comment