> The two things you quote are consistent assuming the services are mostly independent on the server side and it is the client that handles the coordination. A

> The two things you quote are consistent assuming the services are mostly independent on the server side and it is the client that handles the coordination. And if this assumption ceases to hold during the life of the product? For example, I might suddenly want to do some of the client calls from within the server. What then, you scrap the microservice architecture and rebuild it as a monolith? To me this looks really contrary to YAGNI principle. Also, I think handling coordination between internal application stuff on the client is a security can of worms. You are exposing your client to information that he would never see if everything was hidden behind one service.