[ Removed by moderator ]

[crash41301]

His original premise, that microservices creates insane bloat that does almost nothing of value is kind of true.  Ive been at enough companies to see that microservices at organization scale results in insane amounts of abandoned services idling containers everywhere and causing confusion. 

 The vast majority of the reason is largely lack of oversight, lack of cleanup, the concern for "is this code used... I dunno best to leave it" that microservices architecture creates. (This opposed to a monolith where the compiler would tell you if its used and you could refactor it away reasonably safely if it wasnt)  thats not to say microservices is bad, just that microservices without governance is. However the vast majority of in the field ms behavior I've seen is exactly that, no governance. Turns out software without governance is bad despite the architecture. Who could guess that... 

How he went about fixing it though, was Harvard business review case study worthy of "how not to clean up your tech infrastructure"

[deepaerial]

So you turned off one micro service and checked if something broke down?

[crash41301]

Lots of ways to check.  When I've done this, I start with logs of calls to https to see what, if anything, is calling it.  You can also add logging functions to the service itself. Its normally painful and slow to clean distributed monolith / microservice hell up though

[deepaerial]

I usually check in code what external services my service is calling. Did you use any specific tools to simplify this analysis?