Microservice Patterns | Design Patterns | Appended Events
img
Home > Design Patterns > Appended Events

Appended Events (Erl, Naserpour)

How can related asynchronously published events be effectively stored and queried?

Appended Events

Problem

Events processed by a microservice may relate to different tasks and may be published out of sequence, making it difficult to retrieve accurate and complete historical reports for auditing purposes.

Solution

Related events are appended to each other, regardless of the sequence in which they are published. This establishes relationships between the events that allows for accurate and complete auditing and reporting.

Application

The publishing microservice identifies related events that are appended when stored in the event database.

The event publishing microservice associates related events and informs the event store of these relationships, which results in related events being appended. Appended events can then be queried to assist in the generation of accurate and complete auditing reports.

Appended Events: The event data is appended so that related events are associated with each other. This enables the administrator to effectively query the event store for meaningful auditing information.

The event data is appended so that related events are associated with each other. This enables the administrator to effectively query the event store for meaningful auditing information.

This pattern can be applied in different ways, as explained in the complete pattern description.

Module 10: Advanced Microservice Architecture & Containerization.

This pattern is covered in Module 10: Advanced Microservice Architecture & Containerization..

For more information regarding microservice and containerization courses and accreditation,
visit the Microservice Architect Certification program page..