Category: aggregate

Should a Model for a View be an Aggregate with its own Repository?

Should the Model that will be passed to the view be completely defined by a single call to a single repository. In other words, is the Model a single Aggregate, or should my Model be constructed from separate Aggregates, each with its own Repository, in the service layer? The way I have it now, is […]