From Monolith to Observable Microservices using DDD
summary
Shows how Domain Driven Design and event storming pull concrete bounded contexts out of a monolith, isolate them with clean APIs, then extract a delivery microservice for a fast‑fashion retailer used to run live experiments. Implements centralized JSON logs (ELK / Kibana), metric dashboards (Prometheus/Grafana or hosted SaaS), correlation IDs and distributed traces (OpenTracing/Zipkin), and semantic monitoring to verify the hypothesis that extraction does not hurt sales. Iterative refactoring approach, worked in production.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:30Monolith vs Microservices
- 4:40What is DDD
- 9:43Venice Doorman
- 17:47Whats next
- 23:01Observability
- 24:53Logging
- 29:16Semantic Monitoring
- 31:08Dashboards
- 32:40Alerts
- 33:35Not all alerts need human interaction
- 34:32Tracing
- 38:11Conclusion
related talks
01h 02mDeconstructing Monoliths with Domain Driven Design - Rohit Kelapure, David Turanski, Rohit Sood
29mFrom Monolith to Cloud-Ready Microservice Architecture with DDD
24mPatterns of Evolution from Monolith to Microservices
25mData-Driven Migration from Monoliths to Event-Driven Microservices
52mBuilding monolith applications that could scale to microservices..
45mUsing modern .NET technologies to decompose a monolith into micro-services
57mSplitting Monolith Application to Microservices
01h 13mRefactoring to a System of Systems