4.3. Transaction Handling

4.3. Transaction Handling

4.3.1. Set Up

To enable transaction handling based on command dispatch you need to set up the Prooph\EventStoreBusBridge\TransactionManager. The transaction manager acts as command bus AND event store plugin so you need to attach it to both:

/** @var $eventStore Prooph\EventStore\EventStore */

/** @var $commandBus Prooph\ServiceBus\CommandBus */

That's it! Container-Driven Set Up

If you are using the container-aware factories shipped with prooph/service-bus you may also want to auto register the TransactionManager. As long as the command bus is available as service Prooph\ServiceBus\CommandBus in the container you can use the Prooph\EventStoreBusBridge\Container\TransactionManagerFactory for that. Just map the factory to a service name like prooph.transaction_manager and add the service name to the plugin list of the event store configuration. Also have a look at the event store docs for more details about the plugin system.

4.3.2. Features

  1. The transaction manager starts a new event store transaction on every command dispatch. Note: Nested transactions were removed with prooph/event-store v6.0. So you can dispatch follow up commands only after event store commit!
  2. If the dispatched command is an instance of Prooph\Common\Messaging\Message the transaction manager will also add causation metadata to each recorded event during the transaction. Two entries are added to the metadata:
    • causation_id = $command->uuid()->toString()
    • causation_name = $command->messageName(). Note: Depending on the event store adapter used you may need to alter your event stream schema