you'd like to apply domain driven to your old code ? you don't know how ? this talk is for you. i'll introduce few techniques and heuristics based on my experience dealing with legacy code and applying domain driven design concepts on it.
"The Dungeon Master is the author of the original software, that used to support the business in the early days... in facts he knows the software better than anyone else. Even if he’s not any more a software developer, he’s still at close distance from its creation." -- Alberto Brandolino (Inventor of Event Storming) 11
our legacy system/code as a service (as an api for example). Use the Open Host Service (OHS) pattern to publish legacy features on a simpler way that it is. Create bubble context as new feature is needed. 17
context as new feature is asked or bug ﬁxed is asked. If it is a bug ﬁx refactor and extract the feature on new bubble context. Every bubble context has is own way to ask information from legacy using ACL's calling low level services. 21
opportunity. Try to understand how the Legacy system works using event storming and Mob/Pair programing. Work wisely with the Dungeon Master and the Existing System Expert(They can be harmful to the legacy system). Sometimes your level of conﬁdence can be diﬀerent in every slice of the system: combine all the patterns used before (Legacy as Service, OHS, ACL, ...) 23