Design Principles for an Event-Driven Architecture
summary
Covers design principles that connect microservices, Domain-Driven Design and event-driven architecture, with practical examples and governance considerations. Explains how to design an event taxonomy, event enrichment strategies, event correlation/inference, using an event schema registry (e.g., Apache Avro), event traceability, and data reconciliation patterns, plus common challenges and real-time use cases like communications, order management, BAM, KYC and GDPR.
AI-written summary · about
chapters (19)
- 0:00Start
- 0:42Pablo Ruiz Presentation
- 2:38Event Taxonomy
- 5:19Microservices
- 8:28Registry Schema
- 9:34Reference Data
- 10:38Loose Coupling
- 12:11Inference
- 13:07Lineage Traceability
- 14:37Enrichment
- 17:01Orchestration
- 18:36Business Logic
- 19:50Data Reconciliation
- 21:54Consumption Guarantee
- 23:34Monitoring
- 24:14Entity
- 25:11Persistence Layer
- 31:59Questions
- 39:24End
related talks
42mApplication Architectures: The shadows and highlights of Event Driven Design
24mBuilding an Event-Driven Architecture
16mFrom Design to Production: Exploring an Event-Driven Architecture…
31mDemystifying Event-Driven Architectures
47mAccelerating Event-driven Architecture with Domain-driven Design
35mIntroduction to Event-Driven Architectures in 2023
52mNavigating complexity in event-driven architectures: A domain-driven approach
55mNavigating complexity in event-driven architectures: A domain-driven approach