How would you organize an organization with 100 properties? One could say that there are 100s of properties, with several Value objects (since some of the properties have 2 or 3 properties). But the point is how to handle a large number of properties.
I am rebuilding our model from scratch using DDD, and the current problem is how to organize one of the main objects, which is divided into many many subsets. It has now been written that it has about a dozen subsets of properties. Like CarInfo () with 50+ properties, CarRankings () with 80+, CarStats (), CarColor (), etc. Etc.
Think of it as mass data stored in the root of a single object.
Is it appropriate to have a service for the simple purpose of grouping a large set of properties? Like a CarInfoService that will return a Car () object, as well as a large collection or sort.
Another idea is to see how the data is displayed. There is not a single view that would display all this data. Instead, they are divided based on their subjective question. Like CarInfo, all information about the car is displayed. Another will be CarStats, which shows all the statistics of the car. Therefore, in this sense, the application layer can create the basic data necessary for the user interface. But I still need a way to save it in the domain.
I have a mind to just put a whole bunch of bags of xml properties on it and call that day. lol
source
share