November 2025
Intermediate to advanced
464 pages
11h 25m
English
Content preview from Domain-Driven Transformation
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
Start your free trial
Chapter 14. Outlook: Domain Patterns and Their Implementation in Bounded Contexts
Like a Domain-Driven Transformation is never “done,” the method Domain-Driven Transformation is also not “done.” In this chapter we want to share some new and speculative ideas with you that we think can help with future transformations and Domain-Driven Design in general.
In recent years, we have seen a number of domains with their subdomains and have decomposed them. The goal was always to divide one or more software systems among subdomains and to achieve a meaningful decomposition of the software system into bounded contexts based on the boundaries found in the domain. Thus, we were concerned with both the domains and their implementation into bounded contexts. Over time, we gained the following impressions:
-
There are (sub)domains that are easier to decompose into (sub)subdomains, and those where it is significantly more difficult.
-
There are implementations in bounded contexts that make it easier or harder to decompose the legacy system.
-
The development of the domain and the software influence each other, and the legacy software is to be decomposed differently depending on the state of development.
In order to structure the whole thing for us, we have so far identified three domain patterns, and have thought about further aspects in the implementation in bounded contexts.1 We are far from finished with our considerations. We hope that our ideas will spark your interest. We have already had heated ...