Although event processing has been around for a while, it hasn't yet been used widely.
The goal of event-driven architectures is to process information in near real time by reacting to the publication of that information when it happens. Event-driven architectures lower the latency of information propagation while promoting loose coupling between components compared with sequential programming in traditional models.
Event-processing systems have several important fundamental aspects, some of which are as follows:
Push-based messaging pattern: As discussed before, the traditional messaging pattern has been request-response—what can be called a pull messaging pattern because the client pulls information from the server by sending a request. In contrast, in event-processing systems, the event producers push events into the system when they occur.
Autonomous messages: Events are signaled by notifications that are independent of other events (this doesn't mean that event...