There's this one pattern related to aggregates that I often see recurring in projects that start introducing DDD. Even if aggregates are initially built fine they often end up messing feature and business logic. Think about pricing related concept that deals with building an offer.
#ddDesign
1/3
#ddDesign
1/3
Comments
I've done it in similar way in the past.
How do I do it right now?
I delegate those different features/use cases to upper layer
2/3
In Event-Driven Architecture there is a benefit for that. Read models subscribe just to one event (DiscountApplied or sth) instead of all possible features
3/3