Creating User after user registration confirmation: why UserRegistrationConfirmedNotification is not consumed directly by UserAccess?

[forgoty]

I've noticed that single exception when modules are directly call each other is when Registrations module calls UserAccess. This happens as the reaction on UserRegistrationConfirmedNotification.

The question is: why this notification isn't consumed by UserAccess module itself?

[nefosfatus]

Same question. @kgrzybek Please explain why you made an exception in this case? Because registrations and user access are closely related?

[nefosfatus]

@forgoty I read this article and I think I understand it. There are several methods to communicate between modules, each with its own advantages:

Messaging - Ensures the lowest coupling, modularity, and autonomy but comes at the cost of complexity.
Direct Call - Provides lower coupling than Shared Database Data, encapsulates modules, and is relatively simple.
The author, suggests that "most often, when we are talking about modular architecture, it is best to use Direct Call and Messaging together." This shows that we can use the simple Direct Call method when needed.