DDD for Mergers and Acquisitions
summary
Two decades‑old systems from Alporn Autoleasing and Cosmo Cars are compared, not by topic but by exact process: use collaborative modeling (eventstorming, domain storytelling) to map cloud→kite→sea scopes, then perform domain rediscovery to extract subdomains and draw a to‑be context map. Decision criteria are explicit: keep both, migrate data, or combine by selecting the best bounded contexts (sales from one, risk from the other) and apply domain‑driven transformation to modularize and modernize.
AI-written summary · about
chapters (16)
- 0:00Introduction and love story analogy
- 2:00Mergers and legacy systems challenges
- 4:30Case study: Alporn and Cosmo Cars
- 7:27Collaborative modeling explained
- 10:15Understanding scope in modeling
- 13:47Comparing processes at different levels
- 16:35Should we replace one system?
- 17:38Combining and modernizing systems
- 19:29Domain driven transformation
- 22:38Rediscovering domain knowledge
- 25:10Drawing boundaries and context maps
- 27:21Identifying core domains
- 30:38Domain patterns overview
- 37:01De-mergers and spin-offs
- 39:10Key takeaways and lessons learned
- 40:33Q&A session
related talks
51mDomain - Driven Transformation
41mCollaborative Software Design: How to facilitate domain modeling decisions
01h 00mDomain-Driven Architecture at Scale
01h 00mFrom Domain Driven Design DDD to Delivery
39mFrom Domain Boundaries to Software Architecture
47mDomain Driven Transformation—How to Bring Back Sustainable Architecture to
14mFrom Brownfield to Greenfield
38mDomain-Driven Transformation - how to improve the structure of legacy systems