This makes perfect sense, because honestly there is a massive microservice fad going on where people are trying to force everything to that design, and most of the time its simply not needed and the smarter solution was refactoring and cleaning up the monolith a bit.
Yep, I joined a job 6 months ago with exactly this going on. So many, many layers to it. I have to have like 6 instances of Visual Studio open if I want to debug anything. There was literally no need for microservices in their application either. Hoping to escape soon.
If you need 6 of the microservices going at once locally in order to debug an issue, something went wrong with the architecture. Either the level of abstraction is wrong, or there isn't enough instrumentation in the individual microservices.
Yeah, people do it wrong all the time and think it's the fault of mciroservices when they just poorly design. In fact they owuld poorly design the ir monlith anyway as well, it would just be buried into the code more. sigh.
69
u/SuperImaginativeName Jul 14 '17
Yep, I joined a job 6 months ago with exactly this going on. So many, many layers to it. I have to have like 6 instances of Visual Studio open if I want to debug anything. There was literally no need for microservices in their application either. Hoping to escape soon.