Can an aggregate have lite version of another aggregate just for read?
I have an order aggregate with Order as root having multiple OrderLine. OrderLine has "identity reference" to Product aggregate. But having only "identity reference" is not enough. I need value of "taxable" property, last "price" property for calculating price in OrderLine. In fact, in order to calculate price in OrderLine, some data from Product aggregate is needed. How can this problem is resolved in DDD? Is it valid in DDD approach to have a lite version of Product (ProductLite) to use as read-only DTO?
-- UPDATE (thanks to @Francesc Castells)
// app service to add OrderLine
product = productRepo.Read(productId)
orderItemPrice = priceDomainService.CalculatePrice(product.price, product.tax)
order.AddOrderLine(product.ID, orderItemPrice)
orderRepo.Save(order)
Yes, this is perfectly valid. An aggregate should store all data that it needs to fulfill its purpose. This data doesn't have to always be user input, it can also come from other aggregates. There's abviously a difference between data produced by an aggregate and data consumed by it. For example, your Order consumes product prices, but it cannot change the product price and expect the rest of the system to respect that new price, as it doesn't own it.
In your scenario, I would say that once in the OrderLine, the Price is not part of the Product anymore, but part of the OrderLine itself, which could probably be defined as the price of the product the moment it was ordered or maybe the moment it was put in the shopping cart.
- DDD duplicate Entities or not?
- Is MediatR library overused in CQRS examples on the web?
- In DDD(Domain Driven Design), how to persist value objects if they are in separate table with surrogate primary key
- Nestjs Dependency Injection and DDD / Clean Architecture
- Replacing service layer with MediatR - is it worth to do it?
- Best Practices for Managing Unbounded Collections within Domain-Driven Design Aggregates
- Domain Driven Design Application Layer in an ASP.NET application
- Nestjs Event Sourcing - Event Persistence
- DDD - Where should third-party API interfaces should be?
- In DDD(Domain Driven Design), can Repository methods accept Entities or Value Objects that the Aggregate is composed from?
- Prevent exception-based control flow in upper layer of Repository pattern
- Paging in NHibernate
- domain driven design repository
- Using domain driven design entities in an ASP.Net application
- Domain Driven Design Auto Incremented Entity Key
- How to handle paging of sub entities with the repository pattern?
- Is Martin Fowler's POEAA implementation of Unit of Work an anti-pattern?
- If View Model property has value with certain length, replace it with query from database.Do it in Controller, Validation Attribute or somewhere else?
- Is Specification Pattern Pointless?
- DDD Read-Only Repositories returning "value objects"
- DDD driven solution structure
- Using Clean Architecture, am I allowed to Switch Context in Domain Layer ( Use Case )/Or Allowed to use Coroutine Specfic Libraries
- Unsigned number instead of checking invariant in DDD
- Layered architecture, Request and Response DTO, or View Models
- DDD why create interface on domain service?
- Handling Multiple Actors in a Use Case in Clean Architecture and DDD
- Should services always return DTOs, or can they also return domain models?
- DDD Entities making use of Services
- Send, Publish and Request/Response in MassTransit
- CQRS and Domain Driven Design: Anemic data model for Query side