Summary

In this chapter, we have gone into a lot of detail on how to separate out systems and how to deal with concepts throughout the application, mostly on the smaller scale of a project, and how it interacts with the larger scale.

There are many ideas that have been used in other places we can draw from when building the project, be it object-oriented design or be it software architecture patterns; the important thing to keep in mind is that nothing should be set in stone. One very important thing about domain-driven design is that it constantly changes, and that this change is a good thing. As soon as a project becomes too solid, it becomes hard to change and this means the business using it can no longer evolve alongside its software, which ...

Get JavaScript Domain-Driven Design now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.