Microservices guided by DDD and reactive systems paradigm
summary
Argues that combining Domain‑Driven Design for bounded contexts, Promise Theory for dependency contracts, and the Reactive Manifesto for failure handling yields microservices that are modular, service‑oriented and resilient at scale. Recommends designing around aggregates and repositories, modeling events (store, distribute, project) and planning compensations; cites an online banking outage caused by missing timeouts and a 0.3% failure rate that costs millions. Shows three real systems (lending, retail bank, benchmark calculator) and a reference implementation using serverless on AWS functions on GitHub.
AI-written summary · about
chapters (12)
- 0:00Introduction and speaker background
- 2:11Cloud native systems and microservices shift
- 7:29What microservices truly mean
- 15:31Domain-driven design introduction
- 18:20Strategic design with bounded contexts
- 23:58Tactical design in microservices
- 27:50Dependency management with Promise Theory
- 34:55Event-driven systems and reactivity
- 39:08Reactive Manifesto and failure handling
- 41:56Real-world microservices examples
- 45:06When to adopt microservices
- 47:12Key lessons learned in microservices adoption
related talks
48mIT Architecture : All your micro-services are wrong PERIOD!
40mMicroservices without DDD is risky business!
43mPanel: Microservices, Where Did It All Go Wrong
57mEmbracing Microservices
01h 00mMicroservices, Where Did It All Go Wrong?
38mMicroservices, a bittersweet symphony
30mReactive Microservices
47mThe Rise of Reactive Microservices