Event-driven designed systems decouple components, separating ownership of domain data. The loose coupling creates a logical separation between event producers and consumers. Producer services emit events and intentionally do not concern themselves with how the messages are consumed. While subscribing services consume events and intentionally do not concern themselves with how the message was produced, only needing to interpret the payload, you should always aim to have a strict contract between the systems.
Decoupled services can be implemented in different technologies, the right tool for the job, and can be more easily scaled independently of each other. The application or platform inherently becomes more extensible, enabling new features to be onboarded with much less risk of integration regression.