bradjolicoeur / rebus-saga

Rebus Saga Example

This is an example that uses ReBus, RabbitMQ and At the moment uses InMemory for the persistence. The solution is a port of my NServiceBusAWS solution that uses Rebus instead of NServiceBus. The intent is to show a side-by-side implementation of NServiceBus and Rebus to better understand the differences between the two platforms.

There is a docker-compose.yml file at the root of the repo that will spin up an instance of RabbitMQ and hopefully in the near future will also spin up the persistance database.

While this example currently works, it is still work in progress and I have a number of things I plan to add to it.

Workflow

1. Web API controller sends ProcessPayment Command to Saga Endpoint
2. ProcessPayment initializes Saga state in PaymentSaga endpoint and sets a reply timeout
3. ProcessPaymentSaga sends MakePayment Command to PaymentProcessorWorker Endpoint
4. MakePayment handler simulates making a payment and publishes ICompletedMakePayment event
5. ProcessPaymentSaga consumes ICompletedMakePayment, updates state and sends reply to controller
6. Controller displays the results to the caller

If step 4 is delayed, the timeout will triger sending a 'Pending' reply to the controller and the eventual accept message will still get handled in the web api assembly for sending an asyncronous message to the caller.

Note that any keys or passwords included in this repo are provided as examples only. Make sure you update keys and passwords to appropriate values in your system.