I have a NoSQL DB with parts of my data denormalized and duplicated. For concreteness, let's say I have:
- A document set called "people" containing full specifications of people.
- A document set called "votes" containing outcomes of voting rounds in a certain organization. Each vote document has an embedded list of people who voted for and against. The elements of such a list contain a subset of data compared to what's stored in a "people" document.
Is it in accordance or against DDD principles to have two separate model classes in my app, each representing a person - one with the full spec (queried from "people"), one with the subset of data (queried from "votes")? E.g.
It seems to me such a solution falls within the scope of the "bounded context" idea, therefore making it fine, but I want to make sure.