Adv2 Scenario1

Approach #1, two aggregates

The numbers in the diagram correspond to the following steps:

1. The UI sends a command to register X and Y onto conference #157. The command is routed to a new Order aggregate.
2. The Order aggregate invokes a method on a Conference Seats Availability aggregate.
3. The Conference Seats Availability aggregate with an ID of 157 is re-hydrated from the data store.
4. The Conference Seats Availability aggregate updates its total number of seats booked.
5. The updated version of the Conference Seats Availability aggregate is persisted to the data store.
6. The new Order aggregate, with an ID of 4239, is persisted to the data store.