I am not talking about pitfalls of microservices, I am talking about pitfalls of people trying to do microservices. Microservices is not a single idea, but a p

I am not talking about pitfalls of microservices, I am talking about pitfalls of people trying to do microservices. Microservices is not a single idea, but a point in a progression of maturity of various aspects of the application and the team developing it. Think about this, you don't get to be F1 driver just because you decide to. You need to spend a considerable amount of time preparing to be an F1 driver. If your manager (ie. yourself) decides to sit in F1 driver seat but disregards advice to first get years of experience before doing so, this is only going to end in a disaster. And it will not be "a pitfall" of F1 car. Obviously the problem are managers who misplace their focus. "Microservices" is a shiny object everyone wants to brag about but nobody wants to do the ground work necessary. So I see teams that don't even have repeatable build/deployment procedure want to do microservices. Why not have repeatable builds and deployments first? This is already going to improve the situation a lot and be basis for further development which may culminate, at some point, with microservices-style environment.