Giant Swarm

At our last company, we grew quickly. After an initial rush of feature implementations, we were faced with a monolithic app that did not scale well. This reality led us to examine the different requirements within our stack. Our conclusion was that it made more sense to choose the right tool for each job. Rather than the current situation in which the technology of the monolith crippled our agility. By isolating problems into small services we were able to scale in many dimensions. Teams weren't blocking each other. Services could be scaled independently, and we iterated faster. The downside was that up to 30% of our development resources were blocked by infrastructure tasks. Maintaining the infrastructure running so many technologies was simply too distracting and expensive. In 2013, after selling and later leaving the company we started to work on a next-generation highly automated microservices platform. Wherever we demoed it, people wanted to have access to use it too or join the team to work with us on this new infrastructure. Thus the microservices management platform became our next idea - Giant Swarm. Founded