Applying DDD -
summary
SAP builds a single overarching domain model for its Intelligent Enterprise Suite using DDD to replace expensive point‑to‑point mappings, defining concrete heuristics, tooling and org structure. The work narrows hundreds of thousands of semantic entities down to 100–500 entities to align, uses a core team + per-domain alignment groups pattern, generates APIs from the model, applies semantic versioning per domain, starts with reference/master data before transactional data, and adopts the ISO postal standard for messy localizations.
AI-written summary · about
chapters (10)
- 0:00Intro
- 0:39The high level story
- 11:13History: Application internal alignments
- 13:09How DDD makes a difference
- 18:31Design principles and goals for ODM
- 24:19Separation between domain model and representations
- 26:15What entities to address first?
- 29:49Extension pattern - breaking up monolithic structures
- 33:43How to model shared identity
- 37:01Domain model versioning
related talks
44mStrategic Domain-Driven Design for dummies
35mTrivialization of DDD or Not?
39mLessons Learned from 10+ Years with Domain Driven Design
01h 00mFrom Domain Driven Design DDD to Delivery
38mWhat I talk about when I talk about Domain Driven design
56mDDD in Microservices: Complexity versus Complexity
45mDon't Overdose on Domain-Driven Design
42mDomain Driven Design - So Your Code Speaks Plain Language