4 ms·
The point at which you have multiple teams working on the same codebase, and their velocity is suffering from communication overhead and missteps.
by cpitman 7y ago
The point at which you have multiple teams working on the same codebase, and their velocity is suffering from communication overhead and missteps.
- koffiezet 7y agoA few remarks: * Codebase should be defined as 'the platform'. where one team will most likely never look at the code of other team's microservices. * this communication problems and overhead start the moment you go from 2 to 3 or more teams. * the term 'team' in this context should be interpreted very broadly. One dev working alone on a microservice should be considered "a team". Also, things mentioned in the article: you don't want to implement TLS, circuit breakers, retries, ... in every single microservice. Keep them as simple as possible. Adding stuff like that creates bloat very quickly.