This article discusses the definition, value, and practices of aggregation in domain-driven design (DDD)
Hi Gang,Thank you for the great article.I might misunderstood a bit on the part "Consistency of the lifecycle" where you wrote "Consistency of the lifecycle refers to the objects within the aggregation boundary that have a personal dependency relationship with the aggregate root". In your example, the Purchase Item object should disappear when Purchase Requisition is deleted. Does the same rules does not apply when Commodity is deleted because they two different aggregates? If that is the case, should we also rely on "final consistency" to ensure Purchase Item is deleted from Purchase Requisition aggregate? Could you provide an example?Hope you can help to enlighten me.Thanks.
