[disgruntledphd2]

I dunno man, I worked at FB well before the micro services hype and saw a bunch of problems with them, particularly in debugging.

And in general, putting a network boundary between function calls is gonna add a whole bunch of complexity.

That being said, splitting services so that teams could deploy independently definitely also had a lot of benefits at FB, but I could never understand why so many much smaller companies took the micro services approach.

[lolinder]

I'm not into the microservices hype either, I'm just opposed to the reactionary claims in places like TFA that you should basically never split out code into a new service. Both extremes are wrong.

My opinion is that the default should be to keep things in one service and only split them out if there's a very good technical or organizational case to be made.