2 ms·
Consider that the application generally includes includes a client element that has to communicate with the services via HTTP anyway. In that case it often make
by vidarh 10y ago
Consider that the application generally includes includes a client element that has to communicate with the services via HTTP anyway. In that case it often makes little difference if they communicate with a single app or 10. Often you can hide that it is communicating with more than one with a simple load balancer in front of the services.
If the microservices has to do lots of internal communication using HTTP, then you should consider if you've split them along the right boundaries or not.
Sometimes it may not be avoidable, but if there are lots of dependencies between them, then the rationale for splitting them into separate services rapidly drops.
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.
- js8 10y ago> 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.