Events in Drupal allow various system components to interact and communicate with one another while remaining independent, or decoupled. They are one of the ways that module developers can alter or extend Drupal without modifying existing code. (Other ways include Plugins, Hooks, and Services). The system consists of an event dispatcher which is used to trigger a known event at a specific point during code execution. It also consists of a pattern for subscribing in order to be notified whenever an event is triggered by the dispatcher so that your custom code can react.
- Subscribe to an existing event in order to react with custom logic whenever the event occurs
- Dispatch a new event when critical actions happen in your code, giving other components the option to react
The event system in Drupal is unlikely to change for a while. Expect contributed modules to start dispatching events in place of invoking hooks for some types of interactions.
- Technical overview of Drupal’s event dispatching and subscribing systems. Use this if you’re already familiar with the concept of events and you’re just looking for a quick reminder of how the pattern works within Drupal.
Symfony event dispatcher component (symfony.com)
- Documentation for the Symfony event dispatcher, upon which Drupal’s event dispatcher is built. Knowing how it works will help you better understand Drupal’s dispatcher.