Applying (D)DDD and CQ(R)S to Cloud Architectures
summary
Shows a practical migration of a monolith to a split write and read architecture with CQRS and event sourcing, implementing a product management service that publishes create and update events to a message broker (RabbitMQ/streaming) while persisting the write model in MySQL and populating a Lucene/Elasticsearch style search index for reads. Demonstrates event publishers, subscribers, eventual consistency, containerized deployment to cloud, integration testing pitfalls, and that the approach works but needs careful testing and monitoring to avoid stale reads.
AI-written summary · about
chapters (10)
- 0:00Introduction and speaker intro
- 1:57What is Domain-Driven Design?
- 3:55Domain modeling and context mapping
- 6:26Microservices and data ownership
- 9:05Command Query Responsibility Segregation
- 12:19Demo: Product management service
- 17:46Event-driven architecture in action
- 22:42Search and data abstraction
- 25:02Scaling and cloud considerations
- 27:15Q&A and closing remarks
related talks
01h 25mBuilding microservices with event sourcing and CQRS
40mDDD, CQRS, Hexagonal, Onion,... Putting it together
46m" Slicing Monolith into a CQRS / Event sourcing microservice: joys and pains"
01h 07mAn Architecture with CQRS and Event Sourcing
52mBuilding monolith applications that could scale to microservices..
45mBuilding Monoliths that Could Scale (Easily) to Microservices (If They Need)
52mEvent Sourced Transformation in Financial Systems
30mDomain-Driven Design + Command Query Responsibility Segregation + Event Sourcing