From my perspective it is mostly valid for monolith. But microservices are kinda small, simple and isolated, it should be easier to change them.
There are advantages to microservices, but knowing the dependent services is none of them.
If you have a lot of them, keeping track of which services uses which one is a lot of work.
In a monolithic architecture, you have the dependencies in the code base.
I am not saying, that monolithic is better, just that you can see those dependencies better.
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
From my perspective it is mostly valid for monolith.
But microservices are kinda small, simple and isolated, it should be easier to change them.
There are advantages to microservices, but knowing the dependent services is none of them.
If you have a lot of them, keeping track of which services uses which one is a lot of work.
In a monolithic architecture, you have the dependencies in the code base.
I am not saying, that monolithic is better, just that you can see those dependencies better.