Event Interaction
Design the human and system touchpoints where events become decisions, actions and audit trails.
The Event Interaction blueprint focuses on the layer where asynchronous events meet human workflows and synchronous system boundaries. It defines patterns for event-driven command generation, human-in-the-loop decision points, event sourcing for auditability and CQRS for separating read and write models — solving the interaction challenges that arise when event-driven backends must serve real-time user experiences and regulatory review processes.
Key Features
CQRS Read Model Projections
Patterns for building optimised read models from event streams, supporting low-latency queries for dashboards, case management screens and customer-facing status updates.
Human-in-the-Loop Event Patterns
Interaction designs for routing events to human reviewers (e.g. fraud analysts, credit underwriters) with SLA tracking, escalation rules and decision capture back into the event stream.
Event Sourcing for Regulatory Audit
Event store design that provides a complete, immutable history of state changes — satisfying regulatory requirements for decision traceability in lending, KYC and financial crime domains.
Saga and Process Manager Patterns
Long-running process coordination that manages multi-step workflows (e.g. onboarding, remediation) through compensating events rather than distributed transactions.
Use Cases
Fraud Analyst Case Routing
Financial CrimeRouting suspicious transaction events to fraud analysts with enriched context, capturing investigation decisions as events and feeding outcomes back to ML model retraining pipelines.
Lending Application Status Tracking
LendingProjecting credit application events into a real-time status view for customers and internal operations, with full audit trail of every decision and state transition.
Technical Stack
Deliverables
- →Event Interaction Pattern Catalogue(Design document)
- →CQRS and Event Sourcing Reference Implementation(Code repository)
- →Human-in-the-Loop Workflow Specifications(Technical specification)
Expected Programme Outcomes
8–10 weeks
saved on interaction pattern design
87%+
workflow pattern consistency
3–6 months
of interaction rework avoided
95%+
across all event-driven domains
Prerequisites
- →Event-Driven Architecture blueprint adopted or equivalent event infrastructure in place
- →Identified workflows requiring human decision points or regulatory auditability
Interested in Event Interaction?
Speak with our team about how this accelerator can support your engineering programme.
Request this accelerator