Event Driven Architecture at Creditas
summary
An explanation of using event-driven architecture for service-to-service communication at Creditas, a fintech, including pros and cons and motivations for adopting events. Describes how Creditas implemented and validated an Event Driven Architecture in production and shares lessons learned from that deployment.
AI-written summary · about
chapters (15)
- 0:00Start
- 4:08Ubiquitous Language
- 7:53Context Invasion
- 11:34Remote Procedure Invocation (RPC)
- 12:00Simplicity
- 14:55Messaging
- 15:57System Communication
- 17:48CAP Theorem
- 24:03Traditional Model
- 26:48Command Query Separation
- 37:57Application Entry
- 38:15Command Consumption
- 38:57Handling Events
- 40:16Projection - Current State
- 41:01Database
related talks
42mDesign Principles for an Event-Driven Architecture
57mEvent Driven Collaboration
24mBuilding an Event-Driven Architecture
48mEvent-Driven Architecture – Benefits and Pitfalls
16mFrom Design to Production: Exploring an Event-Driven Architecture…
41mGetting started with Event-Driven Architectures in 2023
01h 08mEvent Driven Architecture – Enabling Microservices
31mDemystifying Event-Driven Architectures
