Our team “root” has a field TeamMembers that is a collection of Team Member entities.Īlso, this is a simplified model for the sake of learning. Notice that I’ve modelled the team more closely to what you would expect in an object model. We’ll focus on the Team and Team Member relationships. Let’s refine our model a bit more to get a better understanding of what we’re dealing with. modelling your objects as a relational database). It’s very different that what the standard text-book web application design looks like (i.e. Persistance seems to be a concern that developers struggle with once we start modelling in this way. But for now, let’s look at how this might be persisted. There are still many questions and aggregate specific design heuristics that we’ll look at in future articles. A team member’s role can change per project.Projects can be orphaned for a period of time (i.e.Staff members can be a part of multiple teams.Each team can have multiple staff members associated with it.This design is based off of business considerations like: Here’s what we came up with at the end of the previous article. A brief look at the concern of data duplication.One of the concerns developers seem to have once they learn about aggregates is how does designing aggregates affect my data model & how can I persist them? I want to continue the train-of-thought and dive a bit deeper into further topics. In my last article, we looked at understanding domain-driven aggregates from a basic & simple point-of-view. How do we reconcile our aggregate models and data models? How does this affect how we persist aggregates?
0 kommentar(er)
