Event Streaming Overview

Use event streaming to integrate downstream message systems with MATRIXX. Fully optimize these message systems to filter, transform, and deliver events to multiple secondary targets.

MATRIXX event streaming creates custom event streams from the events that MATRIXX Engine generates. An event stream is an ordered, unbounded, and continuous flow of events. Monitor or analyze event data in real time using an external event-handling solution by creating event streams of specific events relevant to your networks and businesses.

MATRIXX produces events for many reasons. Some events are single data records containing information about actions that occurred in the MATRIXX Engine cluster. If an event impacts multiple wallets, it becomes a primary event and is packaged with the secondary events for those other wallets. When primary and secondary Event Detail Records (EDRs) are generated, they are always in the same MtxEventRecordData MATRIXX Data Container (MDC). For more information about primary and secondary events, see the discussion about EDRs in MATRIXX Integration.

Different events are derived from the MtxEvent object to represent different actions that occur in the system. Some events, such as usage events, are produced often, while other events, such as those for payment processing and records of a purchase, are produced less often.

Event streaming can be used to deliver to a direct target system. For performance reasons, MATRIXX Support recommends that event messaging services to which events are sent be configured for onward delivery.

You can configure multiple streams in parallel. MATRIXX Support recommends that you connect to one to three target systems. A target system, for example, ESB, can offer flexible delivery to other BSS systems for key events such as purchase, cancel, and state changes. That stream can have a more targeted filter configuration.

The Event Streaming Framework streams at least one copy of each event. Typically, only one copy of each event is streamed. Duplicate events might be sent if MATRIXX Engine or Event Streaming Framework encounters processing errors, restarts, fails over, or is processing few transactions per second (TPS). The event consumer takes any action appropriate for duplicate messages. Identify duplicate messages by checking whether they have the same EventId field values. For details about event IDs, see the discussion about MATRIXX event detail records in MATRIXX Architecture.

Figure 1 shows a basic view of the event streaming components and flow. The processing pod sends transactions to the publishing pod. The Event Stream Server generates an event sequence ID for each transaction. The Event Streaming Framework retrieves events from the Event Stream Server. The adapter (with the relevant SDK) loads events to the stream target and then updates the current position in a session object that is stored in the activity database of the processing pod.

Both publishing pods (active and standby) create internal transaction log files that are used for fast failover. For information about recovering event stream data for a system outage or engine failover, see the discussion about MATRIXX transaction logs in MATRIXX Architecture and recovering lost events in this guide.

For a summary of tasks required to deploy event streaming in a MATRIXX environment, see the discussion about implementing event streaming.

For more information about reconfiguring an event stream to change the data type streamed during runtime, see the discussion about configuring event streaming for failed events.