As Bloomz grew beyond million user base, how did build automation help?
Bloomz builds school communication platform that goes by the same name. It is designed to coordinate, communicate and share real-time information among teachers, parents and the PTA. With over a million users Bloomz has been experiencing explosive growth since the start of the 2017 school year and has been adding new educational institutions every day.
Helped by its rich functionality, the Bloomz platform gained wide popularity and attracted a broad customer base. This, in turn, resulted in increased feature requests. As the teams ramped up the development of features across the system, they encountered severe constraints imposed by their shared "QA and Staging environment". In order to deploy the changes - the Dev, QA and Ops had to coordinate continuously. This resulted in the following setbacks:
All of which that Bloomz could have ill afforded in their growth phase!
Bloomz was considering setting up multiple QA environments. This was not just expensive but it also proved to be time-consuming since it required managing multiple dependencies. In addition, setting up and operating parallel environments required technical expertise that would consume the already scarce engineering team's hours.
As Bloomz started looking for ideas from DevOps service providers, they found that either the service providers lacked the experience to work with a complex system such as Bloomz or were very expensive with long timelines and proposed shifting away from Bloomz's existing development workflows.