User InputUser input devices such as a game controller produce events.
RequestsRequests such as a user opening an ecommerce app is an event. Such an event might be consumed by a promotion engine that calculates recommended products and promotional content for the customer.
SensorsSensors are devices that collect data from the real world. Some are designed to stream data while others report information on an event basis. Business rules can trigger an event. For example, if a bank customer transfers more than $10,000 between accounts a business rule might trigger a large-transfer event. That event might be consumed by a security service that checks if that behavior is typical for the customer.Commercially relevant events such as a payment or a signup for a service.
ProcessesA process such as a service provisioning process for a cloud server. For example, milestones in a process can trigger events.
WorkflowThe submission of workflow tasks such as a manager who approves a vacation request.
IntegrationIntegration events such as a supplier who informs an ecommerce site that a product description has been updated.
ErrorsErrors such as a robot that is unable to communicate with one of its sensors.
TimeA timer or scheduler can trigger events.
Complex EventsTriggering events based on a large number of variables. For example, an earthquake detection algorithm that uses multiple variables to confirm that a large earthquake is underway.
Financial EventsFinancial events such as a firm that submits a regulatory filing reporting stock sales by insiders.
NewsCategorized news feeds that are of interest to an algorithm or artificial intelligence. For example, an announcement by a central bank.
|Overview: Event-Driven Architecture|
Implementing functionality by producing and handling events typically using a decoupled publish/subscribe model.