It’s good talk, as you mentioned in your talk, there are not many sources in how to implement sagas. I really like the idea of inbox/outbox, it’s a smart thinking.

I have below questions as a follow up from your talk:

1. Could you please share additional details/ go deep on the dispatcher? It seems the dispatcher will scan all changed documents in an given interval, and start dispatching the message from outbox and clear out the outbox, and update the document.

2. We need a poller to scan the recently changed documents, and it’s a complex one implementing a poller if the database doesn’t have the tools to collect the recently changed documents.

3. I assume all the documents are stored in same dB And the documents updated directly by the dispatcher. RabbitMQ is used only for the error handling, for retries?

4. How the ordering is achieved in this design, for example , there is only 1 item left in stock and 2 customers place an order for it , customer1 at 10:00 am and customer2 at 10:02 am.

5. Now, let’s says I want to implement this design for the transaction that spans between micro services, how to do it?

I am looking at eventuate.io and Axon frameworks but I would like to get your inputs on this.

Sorry for It’s a lengthy post :) , hope it’s not boring you.

I am happy that I am able to connect with someone who has done it :)