The problem that EventEmitter solves is that the time publisher does not need to care who is listening for the event, and the event listener does not care who sends the event, as long as they emit and on on the same EventEmitter object. Such a design will significantly reduce the connection between event publishers and listeners, thereby reducing complexity.
When your event sender and consumer are both in the same module, and there is no need to notify other modules or other modules to care about the events, you can use callback to complete the event sending/monitoring.
The purpose of using EventEmitter is to reduce the coupling between modules Modules pay attention to EventEmitter rather than which module sends the event; at the same time, the module that sends the Event does not care that I send it. Whether there is a response to the event, and whether any module needs this event, this can make the responsibilities of the module clear, and each module only handles the work it should complete
If it is a simple execute callback, then the party that sends the event/generates the event must know who I want to send the event to and which module's callback is called. Whenever a new module needs this event notification, it must be modified on the sending side, and the consuming event side cannot do anything
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
The problem that EventEmitter solves is that the time publisher does not need to care who is listening for the event, and the event listener does not care who sends the event, as long as they emit and on on the same EventEmitter object. Such a design will significantly reduce the connection between event publishers and listeners, thereby reducing complexity.
When your event sender and consumer are both in the same module, and there is no need to notify other modules or other modules to care about the events, you can use callback to complete the event sending/monitoring.
The purpose of using EventEmitter is to reduce the coupling between modules
Modules pay attention to EventEmitter rather than which module sends the event; at the same time, the module that sends the Event does not care that I send it. Whether there is a response to the event, and whether any module needs this event, this can make the responsibilities of the module clear, and each module only handles the work it should complete
If it is a simple execute callback, then the party that sends the event/generates the event must know who I want to send the event to and which module's callback is called. Whenever a new module needs this event notification, it must be modified on the sending side, and the consuming event side cannot do anything