| > The separation of concerns inherent to microservices is such a great advantage It is not. Not even close. You have to manage separate onboarding processes, ensure the standards are completely up to date, ensure that training is extremely relevant and covers every single critical component of the system. You have to maintain up to date documentation of integration state, data flow, testing capabilities, etc. > You can bring an extra hand into the team without them having to have to understand other parts of the code to do their job. That sounds awful. > won't allow you for example to place each service under its own repo which would also provide you with the ability to limit code access Let me guess, you are not paying for engineering talent? The notion of having distributed teams for most of the companies is so ridiculous it's not even funny. What happens if a lead person on team X and Y quits? Are you going to retain a full-time person to manage your deployment process now? What happens if your budget is cut in half and you need to fire half of the team? Do you expect other engineers to pick up something they have not touched for the duration of their stay without slowing down business? > That requires a lot more up-front investment, but it's worth it over the long run None of that is true. |