Designing Events-First Microservices
no recording on file
summary
Covers what events are and what being event-driven means, and advocates using an events-first domain-driven design for microservices. Explains theoretical principles for designing event-driven microservice systems and then gives practical tools, techniques and anti-patterns to apply that design to improve certainty, resilience, scalability, traceability, loose coupling and risk reduction.
AI-written summary · about
related talks
42mDesign Principles for an Event-Driven Architecture
58mImplementing Event-driven Microservices
48mDesign principles to the rescue of micro-services
47mEvent-Driven Microservices = Microservices Done Right
52mBest Practices in Event-Driven Application Design
39mMicroservices: Improving Team Management with Event Driven Architecture
56mMicroservices and Domain-Driven Design — The Strategic Parts
59mImplementing Event-Driven Microservices architecture in Functional language