Reactive DDD—When Concurrent Waxes Fluent
summary
Argues that Domain-Driven Design plus reactive actor-based messaging makes concurrency fluent and type-safe, demonstrates an open-source platform Vlingo (Java/.NET, MPLv2) that runs fully async, clustered, with optional event sourcing and multiple persistence strategies. Proposes a concrete idempotency pattern using a progress value object to absorb at-least-once delivery and unordered events. Recommends strangler migration (DB triggers or Oracle GoldenGate) from legacy monoliths, warns tiny microservices scale cost‑wise (~$400/month per service; 20,000 services ≈ $8M/month).
AI-written summary · about
chapters (15)
- 0:00Reactive DDD When Concurrent Waxes Fluent
- 3:13Reactive Platform Chief Architect
- 8:06Blocking HTTP
- 11:47Anemic "Domain Model"
- 18:32Bounded Context
- 23:05Event Driven
- 25:04Protocol
- 29:58Type Safe?
- 37:46Business Wants
- 38:23Definitions
- 38:53Legacy: Monolith
- 45:27Explicit, Testable, Less Code
- 49:54Strangler (2)
- 52:00Architecture
- 54:50Open Source Reactive Platform
