As Bloomz grew beyond million user base, how did build automation help?
Bloomz builds school communication platform by the same name, designed to coordinate, communicate and share real-time information between teachers, parents and the PTA. Bloomz has over million users and experiencing explosive growth since the start of 2017 school year, adding new educational institutions everyday.
Bloomz platform's rich functionality helped spread its reputation, attracting a huge customer base. This in turn increased the feature requests. As teams ramped up features development across the system, they kept hitting severe constraints imposed by their shared "QA, Staging environment". Dev, QA, Ops had to continuously coordinate to deploy the changes. This :
which Bloomz could ill afford in this growth phase.
Bloomz explored setting up multiple QA environments. But multiple QA environments was expensive and time consuming, having to manage multiple dependencies. In addition, setup and operation of parallel environments required technical expertise consuming already scarce engineering team hours.
Bloomz started looking for ideas from devops service providers. Either the service providers did not have experience to work with a complex system such as Bloomz (or) were very expensive with long timelines, proposed shift away from Bloomz's existing development workflows.