From a Monolith to Microservices
Our little application has started gaining traction, and the business has asked us to redesign our API while keeping the previous version running to ease the transition. So far, we have implemented a “monolith” – all of our application is deployed as a single item. Our team is very busy with evolutive maintenance, which we cannot defer. Then, our management has a “Eureka!” moment: let’s add more staff.
Most engineering management books recommend that the team size should never increase beyond eight people – or if you’re Amazon, no larger than the amount that can share two large pizzas (that’s Jeff Bezos’s two-pizza rule). The reason is that with over eight people, the number of interconnections between team members grows exponentially, making collaboration impossible. An often overlooked solution is to not grow the team, but rather slow down delivery.
A solution to our growing...
