Take inspiration from Sharpino.Sample.10, particularly considering the IncrementCounterAndAccounts, which arranges any command of two types. Find use cases where this makes sense. Example: add X reservations, Y payments, Z cancellations, Q refunds related to a set of rooms, users, accounts.
Sometimes the same object may be interested by different actions (i.e. a reservation and a payment at the same time). That's fine, as long as the tests show that it fits.
If it is not possible or too hard, explain why.
Take inspiration from Sharpino.Sample.10, particularly considering the
IncrementCounterAndAccounts, which arranges any command of two types. Find use cases where this makes sense. Example: add X reservations, Y payments, Z cancellations, Q refunds related to a set of rooms, users, accounts.Sometimes the same object may be interested by different actions (i.e. a reservation and a payment at the same time). That's fine, as long as the tests show that it fits.
If it is not possible or too hard, explain why.