[vidarh]

If you can replace the "distributed objects" from the original article and substitute it with the word "microservices" then your guilty party are doing microservices in a way Fowler was arguing against even for distributed objects all those years ago.

Doing microservices right involves taking the advice in the linked article: Avoid splitting services when there is no need to; certainly avoid splitting at object/class boundaries - split out functional units that require little communication between them (ideally, split only out things that can fully serve requests from the client, and mediate state in other ways, like e.g. authentatication tokens or signed state); think about latency.

It's about refining the thinking about when it is right to split services up and how to do it without falling in the "CORBA trap" where people tried to make objects metaphorically "floating around the network" for now good reason.