Exploring Domain-Driven Design and Semantics
The previous chapter ended with a promise to provide a method to deal with a pivotal format and the design of an evolution-ready, functionally correct entity when no standard exists in this precise domain. This is the subject of our present chapter.
In order to reach this objective, a very important prerequisite is to keep thinking in functional terms. I know most of you will certainly have a technical background and may wonder when we are finally going to get to the code. Having you wait this long without doing anything technical has been done on purpose and is part of the pedagogical journey provided by the reading of this book. You have to stick to functional and business-related concepts as long as you can because, as soon as you transform this knowledge into software, it gets solidified and way harder to modify afterward. I promise that, as soon as the next chapter, we will start getting our hands dirty with some technical decisions...
