DDD + Microservices + DevOps – The Strangler Figs Way
summary
A 30‑year monolith at a major bank gets rebuilt incrementally using Domain‑Driven Design, the strangler pattern and DevOps with Docker on OpenShift/Kubernetes, CI/CD, Kafka streaming, ELK/Kibana, Couchbase/GemFire. Teams extract stored‑procedure logic into domain services, introduce a service proxy to route calls, and replicate three legacy databases while handling 21–23 days for some data migrations. A single endpoint once returned 40,000+ attributes in a 1.3MB payload. Result: faster releases, lower operations cost and restored scalability via incremental deployments.
AI-written summary · about
chapters (9)
- 0:00Introduction and background
- 7:06Problem statement and goals
- 8:29Domain-driven design approach
- 10:35Database transformation strategy
- 13:22Microservices and data migration
- 15:50Batch processing and APIs
- 18:18Service proxy pattern
- 20:01Final architecture overview
- 23:15Business benefits and metrics
related talks
47mFrom Monolith to Microservices With the Strangler Pattern
24mModernise your monolith using strangler pattern
33mFireside chat - Monoliths, Microservices & Modernization – Practical Strategies
40mFrom Monolith to Observable Microservices using DDD
44mRoute to microservices the epic voyage of a fintech leader
48mThirty months of microservices
30mApplication Modernization Using Cloud Strangler Pattern and DevOps Best Practices
48mFrom Monolith to Micro-services with Kubernetes