Overview

Chapter 5. Consuming the events

In this chapter, the focus shifts from event producers to their mirror image: event consumers, the entities that accept event objects from an event processing network and act on them. The chapter explains the consumer definition element as the model’s representation of a consumer node, emphasizing that it describes only how the consumer connects to the network, not the consumer’s internal logic. It can stand for an abstract type, a class of instances, or a single concrete instance, and its description includes identifying details, input terminals, and relationships to other consumer definitions.

The text then broadens into the main kinds of consumers and how they are used in practice. Hardware consumers are described as actuators that carry out physical actions in response to events, such as opening valves or controlling machinery. Human-facing consumers include alerting systems, dashboards, visual displays, feeds, and social-network notifications, all of which present event information in ways suited to monitoring or decision support. Software consumers include event logs for diagnostics and audit trails, as well as business applications and BPM or workflow systems that use events to start, stop, or advance business processes.

The chapter also explains how consumers interact with the rest of the network, especially when a consumer definition represents a class of multiple instances. In such cases, consumers may be dynamically subscribed and unsubscribed, and events may need routing to only the relevant members of the class based on event attributes and filters. The final example applies these ideas to the Fast Flower Delivery application, where drivers, stores, and the Drivers’ Guild are modeled as consumers with different terminals and event types. Overall, the chapter concludes by showing how consumer modeling helps connect event processing to real-world actions, user interfaces, and business systems.

An event consumer with two input terminals
The event consumer definition element contains details about the definition element itself, a list of input terminals, and a list of relationships to other event consumer definitions.
An event consumer with an explicitly modeled channel as the source for its input terminal
Kinds of event consumers encountered in event processing applications
Performance monitoring dashboard. This event consumer takes a variety of performance measurement events and displays them as graphs.
A dashboard screen showing the use of color-coding to indicate out-of-line situations. The window at the top right indicates that all the resources being monitored exceeded the maximum acceptable value for path latency.
The Ambient Orb. The orb can be programmed to change color to reflect the general health of an organization, or to show the status of a specific key indicator.
A visual display from a location tracking application. The individual markers show the positions that a particular vehicle (in this case a bus) has visited in the previous 24 hours.
Twitter can be used to report the position of a vehicle.
A simple business process modeled using BPMN. A process instance is created when a new order is received and proceeds through a sequence of activities.

FAQ

What is an event consumer in an event processing network?An event consumer is the logical complement of an event producer. It accepts event objects from entities in an event processing network and processes them. In the EPN model, its internal processing logic is outside the scope of the model.
How is an event consumer represented in the EPN model?An event consumer is represented as an event processing network node that has only input terminals. This node can stand for either a single consumer instance or a class of similar consumer instances.
What are the three ways an event consumer definition element can be used?The event consumer definition element can represent: an abstract event consumer type, a class of concrete event consumer instances, or a single concrete event consumer instance.
What information is included in the event consumer details section?The event consumer details section includes an event consumer identifier, an event consumer category, a definition element type, and an optional annotation. These describe the consumer or consumers represented by the definition element.
What are the main attributes of an input terminal on an event consumer?An input terminal has an identifier, a list of event types, optional filters, and a list of sources. The event types act as a basic filter, while additional filters can further restrict which events are accepted.
What kinds of event consumers are described in the chapter?The chapter groups event consumers into three broad families: hardware consumers, software consumers, and human-interaction consumers. These categories are not rigid, and real systems may combine elements of more than one family.
What is a hardware event consumer?A hardware event consumer is often called an actuator. It reacts to incoming events by performing a physical action, such as locking a door, turning equipment on or off, or opening a valve.
What are examples of human-interaction event consumers?Examples include alarm systems, email or SMS notification generators, dashboards, visual tracking displays, travel boards, sports scoreboards, web feeds, and social media postings such as Twitter updates.
What is the difference between an event consumer and a subscriber?An event consumer is the entity that receives and processes events, while a subscriber is the entity that submits a request to register a consumer instance. Often they are the same, but not always, since one entity can subscribe on behalf of another.
How does the Fast Flower Delivery example use event consumers?It defines three consumers: Driver, Store, and Drivers' Guild. Driver and Store are consumer classes with multiple input terminals, while Drivers' Guild is a single consumer instance that receives evaluation reports through one input terminal.

pro $24.99 per month

  • access to all Manning books, MEAPs, liveVideos, liveProjects, and audiobooks!
  • choose one free eBook per month to keep
  • exclusive 50% discount on all purchases
  • renews monthly, pause or cancel renewal anytime

lite $19.99 per month

  • access to all Manning books, including MEAPs!

team

5, 10 or 20 seats+ for your team - learn more


Close
choose your plan

team

monthly
annual
$49.99
$499.99
only $41.67 per month
  • five seats for your team
  • access to all Manning books, MEAPs, liveVideos, liveProjects, and audiobooks!
  • choose another free product every time you renew
  • choose twelve free products per year
  • exclusive 50% discount on all purchases
  • renews monthly, pause or cancel renewal anytime
  • renews annually, pause or cancel renewal anytime
  • Event Processing in Action Event Processing in Action ebook for free