In part one of this series, we started defining the problem we are solving. Essentially, we are trying to leverage Docker and DevOps tools to ensure our decentralized team can release faster and with less centralized synchronisation. Before we dive into software choices, we have to talk about the elephant in the room.
Tl;dr — Load Impact is growing, and one of the challenges with growth is making sure your infrastructure and development cycle mature with that success. This is Part 1 of our series, “The Road to Microservices.” Here’s what we’ll cover:
- Why we decided to make the change to a microservice-oriented approach
- We’re switching to Docker! (Isn’t everyone, at this point?)
- What we expect to get out of these changes