Merge Hells! Feature toggles to the rescue
Speaker: Leena S N
Duration: 40 min
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.
Leea S N
Over the last 13 years, I've played the following roles:
In the recent past I've been playing significant role in streamlining the delivery process using Continuous Delivery and Kanban. I've written and spoken about Setting up of Continuous Delivery for both Mobile and Web Applications(mainly Ruby on Rails Apps)
I've spoken about CD during DroidCon India 2011 and AgileIndia 2012. I’ve also conducted workshops on TDD in Android using Roboletric during Droidcon India 2014 and TDD in Angular.js during Angular MiniConf 2014 and also at RootConf 2014.