Book Image

JavaScript Domain-Driven Design

Book Image

JavaScript Domain-Driven Design

Overview of this book

Table of Contents (15 chapters)
JavaScript Domain-Driven Design
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
Index

Sharing knowledge


We split the application apart into multiple sub-applications of the sub-domains, we do this to increase the size of the team and enable better cooperation between them. This also means that the team needs to find a way to share the information about the application and their usage with new developers as well as with developers tapping into the sub-domain to accomplish a certain goal.

The domain language is an important part of our design and we invested some time into building it throughout the development so far. We can draw on this and make this language available for other developers. The language, as we have seen it, slightly adjusts for each module and is a working document that needs to be kept up to date, and that means we need to find a way to keep it published.

The publishing language

The language we have been developing is an ever-evolving document, and as such we have to think about how to share the knowledge embedded in it. Again let's first define what we would...