Feature toggle

A feature toggle,[1] (also feature switch, feature flag, feature flipper, conditional feature, etc.) is a technique in software development that attempts to provide an alternative to maintaining multiple source-code branches (known as feature branches).

Continuous release and continuous deployment provide developers with rapid feedback about their coding. This requires the integration of their code changes as early as possible. Feature branches introduce a bypass to this process. Feature toggles bring developers back to the track, but the execution paths of their features are still "dead" if a toggle is "off". But the effort is low to enable the new execution paths just by setting a toggle to "on".

The technique allows developers to release a version of a product that has unfinished features. These unfinished feature are hidden (toggled) so they do not appear in the user interface. This allows many small incremental versions of software to be delivered without the cost of constant branching and merging.

Whilst the pattern can be implemented very simply in most programming languages, there are libraries [2] available to further simplify usage.

Fowler states that a feature toggle is the second-best solution. The best solution is to find a way to gradually integrate without feature branches or feature toggles.

Feature-toggling is used by many large websites including Flickr,[3] Disqus,[4] Etsy,[5] Gmail and Netflix.[6]

References

  1. ↑ Martin Fowler 29 October 2010 (2010-10-29). "FeatureToggle". Martinfowler.com. Retrieved 2013-09-27.
  2. ↑ One of many feature toggle framework list: http://www.beautifulbuilds.com/feature-toggle-frameworks-list/
  3. ↑ http://code.flickr.net/2009/12/02/flipping-out/
  4. ↑ http://blog.disqus.com/post/789540337/partial-deployment-with-feature-switches
  5. ↑ http://codeascraft.com/2011/02/04/how-does-etsy-manage-development-and-operations/
  6. ↑ http://techblog.netflix.com/2013/11/preparing-netflix-api-for-deployment.html

External links

Tools