4 ms·
This is a very good point, and you could probably write quite a few articles about this particular subject. You may even have a service A that calls service B
by Freebytes 3y ago
This is a very good point, and you could probably write quite a few articles about this particular subject. You may even have a service A that calls service B that calls service C that calls service A. Then you have a problem. Or, you have C get blocked by something happening in A that was unexpected. Ideally, you only have parents calling children without relying on the parents whatsoever, and if you fail in this, you have failed in your architecture.
- andreygrehov 3y agoI think Robert C. Martin has already described that fairly well [1] [2]. [1] https://www.youtube.com/watch?v=N7agCpAYp1Q https://www.youtube.com/watch?v=N7agCpAYp1Q [2] https://en.wikipedia.org/wiki/Acyclic_dependencies_principle https://en.wikipedia.org/wiki/Acyclic_dependencies_principle