Master Data Management
In the previous chapter, we showed you a method to design information entities in such a way that they do not have any technical coupling, in an effort for the information system containing them to be free to evolve when the business changes. If the data model is a pure reflection of the business represented, it makes it much easier to follow business changes (and change is the only constant) because there won’t be some technical constraint in our way forcing us to compromise on the quality of the design, and thus on the performance of the system as a whole.
In this chapter, we will start talking about the implementation of the data model into something concrete (if this can be said about software, which is mostly virtual). It is only in Chapters 16 to 19 that we will code what we will call for the rest of the book the “data referential(s)”. For now, we will start some actual software architecture to welcome the data model, persist the...
