liveBook · Manning

Event correlation

As explained in Kafka for Architects

Event correlation is the association of related events or workflows through a shared identifier or contextual relationship.

Event correlation associates related events or workflows through shared identifiers or contextual relationships, preserving business context across distributed processing. section 10.1.3

It becomes important when a business process spans several events and cannot proceed until related decisions, such as risk and compliance checks, are connected. section 10.1.3

Approval workflow

Correlate risk and compliance events with an applicationId or caseId so the approval workflow retains context across distributed events. section 10.1.3

Design considerations include:

  • Choose a shared identifier that remains available across the participating events or workflows. section 10.1.3
  • Formalize the related business events and their schemas in Kafka topic requirements. section 10.1.3

How Kafka for Architects covers it

How deep it goes
Defines shared-identifier correlation and illustrates its role in approvals, but stops short of implementation details.
Examples
Uses approval workflows that combine risk and compliance checks through applicationId or caseId.
What it assumes
Assumes familiarity with business events and Kafka use-case definition.
What you can do after
Evaluate/understand when workflows require correlation and specify identifiers for their Kafka-backed event requirements.
How it connects
Connects event correlation with Kafka topics, event schemas, distributed workflows, and idempotent consumers.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Kafka for Architects. The section links point to the parts of the book it draws on.