In this chapter, we looked at the various ways domain-driven design is influenced and can be augmented by related software development patterns. Some patterns are closer than others, such as DSLs, and some are more orthogonal such as modeling the system as a series of events.

The important thing is to make sure we don't get stuck in trying to only apply the techniques we see in a specific pattern, but look at what is around to make sure we use the right tool for the job. At its core, domain-driven design is about modeling business software, and while most business software follows similar patterns and rules, some internal details might be very well-suited for a functional core integrated in the software as a whole, or even the development of a DSL that allows not-so-technical business experts to express their rules clearly.

In the next chapter, we are going to sum up all the details we came across and are going to think about how to work on an ever-changing product like most business...