{"id":27881,"date":"2019-12-25T00:00:00","date_gmt":"2019-12-24T23:00:00","guid":{"rendered":"https:\/\/blexin.com\/orchestrare-gli-eventi-con-rebus\/"},"modified":"2021-05-21T20:30:32","modified_gmt":"2021-05-21T18:30:32","slug":"orchestrate-events-with-rebus","status":"publish","type":"post","link":"https:\/\/blexin.com\/en\/blog-en\/orchestrate-events-with-rebus\/","title":{"rendered":"Orchestrate events with Rebus"},"content":{"rendered":"\n
\"\"<\/figure>\n\n\n\n

In the\u00a0previous article<\/a>, we saw how the use of a service bus could\u00a0benefit software systems where the decoupling between their parts is necessary. In particular, we have seen how to do that with Rebus.<\/p>\n\n\n\n

Rebus makes available a very interesting feature: the ability to orchestrate processes with a long duration (long-running process), and whose evolution is not sequential but based on the unleashing of events.
For this type of process, in literature, we can find the Process Manager Pattern<\/a>.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

The process manager is triggered by an event (trigger message) and acts as a central control unit managing the status of the sequence of steps of the process and deciding the actions to be taken based on intermediate results.<\/p>\n\n\n\n

With Rebus, it is possible to model such scenarios as it provides the so-called Sagas<\/strong>. Saga is just another name for Process Manager, and so a saga is nothing but the implementation of a state machine whose transitions between states are determined by messages.<\/p>\n\n\n\n

To achieve this implementation, we need:<\/p>\n\n\n\n