Regarding dispatcher

Agentic Automation
1

Hi all,

I have a question

  1. At what scenario we need to use single re framework for both dispatcher and performer .
  2. At what scenario we need to use separate dispatcher abs performer processes??
2

Hi @naveen.s

If there are no specific considerations, such as adding transactions to the Queue and using a Queue Trigger to trigger the Performer, then it’s best to use separate reframework workflows for the Dispatcher and Performer. Otherwise, you can use a single REFramework for both.

Hope this helps!

3

In bellow scenarios you can think of not using ReFramewok as dispatcher.

  1. Simple process where you are not expecting any error in input file.
  2. You just need to push small data from excel to Queue.
  3. Where you don’t want any logging.

Still I would suggest to use ReFramework as linear process just for scalability if requirement changes in future.

Note. DU Process can be use as dispatcher where you have DU use case

4

Use a single RE Framework when dispatching and performing are closely linked, transactions are few, and immediate processing is required.

Use separate dispatcher and performer processes when dealing with large-scale, parallel, or asynchronous processing that requires better scalability and efficiency.

Regards,
Arivu

5

@naveen.s

ideally when you dont have any much preprocessing steps before adding to queue and if bulk add queue items can be used then its better you go with single

in scenarios like preprocessing steps involved for each transaction then separate is used

cheers

6

The concept of RE Framework best suited for transactional process. Means - same actions are repeated for every record in the queue.

Dispatcher is considered to be the process which add these records to the queue. and the RE Framework is used for processing these records.

In short - it is always better to separate dispatcher and performer. Dispatcher - You can build yourself and no need to use RE Framework. Performer - Always suggested to use RE Framework