Feature Toggle- What Why and How

Feature Toggle provides a mechanism for including pending features that take longer than a single release cycle as a part of CI/CD. 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 delivered version. When the feature is done and complete we can have it as part of the release and the toggle is then removed.

This session will cover the basics of Feature Toggle along with a technical walk through of code in the session to understand what is Feature Toggle, why we need it and what are the business contexts in which we can use it. The live demo will cover the libraries that support Feature Toggle and we can also talk about the design patterns that can and should be used with this feature. The session will enable us to understand when to use Feature Toggle and what are the lessons learnt on its usage.

2 favorite thumb_down thumb_up 0 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist

Outline/structure of the Session

The high level agenda of the session will be :

  • What is Feature Toggle
  • Business context –Why we need Feature Toggle
  • Types of Toggles
  • Considerations when using toggles
  • How – Technical Implementation 
  • Lessons Learnt

Learning Outcome

At the end of the session the audience would walk away with the understanding of feature toggle and how we can use it. They will understand when and when not to use this feature and how this adds value and makes for a "lean" the development cycle.

Target Audience

Developers, QA Manager, CI Team

schedule Submitted 1 year ago

Comments Subscribe to Comments

comment Comment on this Proposal

  • Liked Kalpna Gulati

    Kalpna Gulati - Service Virtualization - An arm that comes "HANDY"

    30 Mins

    As the software industry moves from the Monolithic to absolutely componentized Service oriented architecture paradigm, it is not generally uncommon to have integrations almost always and dependencies quite often between several services. With the world being open to using third party already built up services it is a common scenario where world class products integrate with vendor provided services. All these lead to a problem of having interdependencies on these vendors or service providers that may be internal cross geographic teams or external vendors.