I'm an advocate for giving every event a Correlation ID copied from the command that caused it.
OrderAccepted → OrderPaid → OrderShipped
All share CorrelationId: "ABC123"
Now you can... 👇
OrderAccepted → OrderPaid → OrderShipped
All share CorrelationId: "ABC123"
Now you can... 👇
October 9, 2025 at 8:24 AM
I'm an advocate for giving every event a Correlation ID copied from the command that caused it.
OrderAccepted → OrderPaid → OrderShipped
All share CorrelationId: "ABC123"
Now you can... 👇
OrderAccepted → OrderPaid → OrderShipped
All share CorrelationId: "ABC123"
Now you can... 👇
Common Event Sourcing mistake: multiple aggregates in one stream.
One stream = One aggregate
Customer[123] stream → CustomerRegistered, EmailChanged, AddressUpdated
Order[456] stream → OrderPlaced, ItemAdded, OrderShipped
Different streams. Different things.
One stream = One aggregate
Customer[123] stream → CustomerRegistered, EmailChanged, AddressUpdated
Order[456] stream → OrderPlaced, ItemAdded, OrderShipped
Different streams. Different things.
October 10, 2025 at 8:24 AM
Common Event Sourcing mistake: multiple aggregates in one stream.
One stream = One aggregate
Customer[123] stream → CustomerRegistered, EmailChanged, AddressUpdated
Order[456] stream → OrderPlaced, ItemAdded, OrderShipped
Different streams. Different things.
One stream = One aggregate
Customer[123] stream → CustomerRegistered, EmailChanged, AddressUpdated
Order[456] stream → OrderPlaced, ItemAdded, OrderShipped
Different streams. Different things.
August 27, 2026 at 7:49 PM
Publish OrderShipped only when both OrderPlaced and OrderBilled have been successfully processed…how do we do that from stateless message handlers? Check out our #NServiceBus #Saga tutorial https://docs.particular.net/tutorials/nservicebus-sagas/1-saga-basics/
NServiceBus sagas: Saga basics
A step-by-step guide to building an NServiceBus saga to handle a common business case of taking action once multiple messages have been successfully received.
docs.particular.net
September 10, 2025 at 3:04 AM
Publish OrderShipped only when both OrderPlaced and OrderBilled have been successfully processed…how do we do that from stateless message handlers? Check out our #NServiceBus #Saga tutorial https://docs.particular.net/tutorials/nservicebus-sagas/1-saga-basics/