Have you ever wondered how Amazon does deployments in every 11 seconds? Have you ever wondered how frequently Google Chrome updates?

Compare that with an enterprise product you are using or the banking application that you use, it takes weeks or even months for an update. The assumption is that frequent releases are possible for Googles or Amazons or Unicorns. It is not for others.
This talk is about why that assumption is wrong. It can be done anywhere, with enough focus and investment for the Continuous Delivery pipeline to make sure that every commit is releasable or deployable.

And fundamental to Continuous Delivery is Continuous Integration. Continuous Integration guarantees every change committed to the repository is tested and reported about production readiness. And Feature Toggle is for turning features on/off depending upon certain conditions. This opens the opportunity to test certain features quickly with few users for experimentation and learning.

Feature branching has been popular for long, but everyone knows about the “code merge hell”, a common issue because of long-lived branches or infrequent integration. If the team is spending time in fixing the merge hells and checking what part of the code needs to be merged, then it is not the efficient use of human talent.

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

Outline/structure of the Session

- A small story about the typical last mile issue in Software Delivery

- Importance of Continuous Integration and its relation with Trunk based/Mainline development

- Feature toggles

- Types of Toggles

- Dark Side of Toggles

- Conclusion

Learning Outcome

Feature Toggle is one of the key practices for Continuous Delivery, but not enough has spoken about the same. This session is to give an intro about Feature Toggle and explain the advantages it has over Feature branching and share my experience while using it for the last few years.

Feature toggles are supposed to be short lived, and if not, can contribute to Technical Debt. The session will touch upon the same too.

Target Audience

programmers, architects

schedule Submitted 4 months ago

Comments Subscribe to Comments

comment Comment on this Proposal
  • Michael Sahota
    By Michael Sahota  ~  3 months ago
    reply Reply

    Is the title supposed to say Merge?

    • Leena S N
      By Leena S N  ~  3 months ago
      reply Reply

      Hi Michael,

      I didn't get your question correctly, can you be more clear?

      The title has the word "Merge" in it because the idea is to convey the issues with not merging to a single branch [aka Trunk or Mainline] as frequently as possible to avoid issues which can create delays in deployment. 

      Thanks,