According to Wikipedia, an Event-driven Architecture, is a software architecture pattern that promotes the production, detection, consumption of, and reaction to events.
There is a perfect pairing between microservice-based architectures, Domain Driven Design (DDD) and event-driven architectures. In this conference we will review what design principles are the catalyst for this symbiosis as well as practical examples in different areas including governance. Many business use cases can be articulated on top of these principles, abstracting them from both complexity and variability in the technological stack.
As a good part of the audience will already be dealing with events and microservices, we will also explain other key concepts:
- Designing a future-proof event taxonomy.
- Strategies for event enrichment, starting with the definition of that concept.
- Managing correlation or inference of events.
- Benefits from an event schema registry using for example Apache Avro.
- Traceability of events by design.
- Data conciliation patterns, and when to avoid it.
We will also take advantage of the opportunity to discuss about common challenges (and others not that common), frequent mistakes and how to avoid or mitigate them.
To conclude, we will explain some use cases that we are solving superbly based on real-time events: Communications, Order Management, Business Activity Monitoring (BAM), KYC, GDPR...
Todos los vídeos de Commitconf 2019 en: https://lk.autentia.com/Commit19-YouTube