This guide should be a little less accepting of synchronous calls between µservices. Once you have a synchronous call between µservices you have done nothing except introduce a relatively slow call and potential point of failure to what used to be a super fast method call in a monolith. Synchronous communications between µservices should be avoided if at all possible.
However, this is a nice guide and I do like the fact it favors pragmatism over dogmatism and sometimes synchronous calls are necessary (or at least the easiest solution). Try to keep them to a minimum though.
Our company banned this. Each service must listen to queues for data and maintain their own datastores. This has dramatically increased reliability and stability.
It's a different mindset. Maintainability hasn't been the problem. Complexity becomes a problem though. I think the microservice patterns we're using today will be revised soon as the industry learns more about this. Having to consume everything from queues and maintaining your own datastores is a lot of work.
24
u/wildjokers Dec 12 '19 edited Dec 12 '19
This guide should be a little less accepting of synchronous calls between µservices. Once you have a synchronous call between µservices you have done nothing except introduce a relatively slow call and potential point of failure to what used to be a super fast method call in a monolith. Synchronous communications between µservices should be avoided if at all possible.
However, this is a nice guide and I do like the fact it favors pragmatism over dogmatism and sometimes synchronous calls are necessary (or at least the easiest solution). Try to keep them to a minimum though.