In an event sourcing architecture, what is the typical pattern for passing information about related objects (aggregates)?
For example, in a order processing system, should
OrderCreated event (published by the
productId or a
Assuming there's also a
ProductService), with the first option, receivers of the event can call the
ProductService to get the
Product and with the second option all the information it needs are already in the event. But I'm not quite clear on the pros and cons of the two approaches. Can someone shed some light?