0% found this document useful (0 votes)
45 views3 pages

UiPath Architecture 1684225200

The document describes 14 different robotic process automation architectures: Dispatcher-Performer, Long Running Workflows, Multi-Stage Processing, Priority-Based Processing, Retry Mechanism, Parallel Processing, High Availability, Elastic Scalability, Distributed Processing, Event-Driven, Failover, Service-Oriented, Pipeline, and Hybrid. These architectures provide different approaches to structuring how robots and tasks are organized to optimize for factors like workload distribution, complex tasks, priorities, failures, and varying demands over time. Real-world implementations may combine elements of different architectures to meet specific system requirements.

Uploaded by

prashan
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
45 views3 pages

UiPath Architecture 1684225200

The document describes 14 different robotic process automation architectures: Dispatcher-Performer, Long Running Workflows, Multi-Stage Processing, Priority-Based Processing, Retry Mechanism, Parallel Processing, High Availability, Elastic Scalability, Distributed Processing, Event-Driven, Failover, Service-Oriented, Pipeline, and Hybrid. These architectures provide different approaches to structuring how robots and tasks are organized to optimize for factors like workload distribution, complex tasks, priorities, failures, and varying demands over time. Real-world implementations may combine elements of different architectures to meet specific system requirements.

Uploaded by

prashan
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

Franck MONGO – UIPATH MVP – IA RPA BPM CONSULTANT – hyperautomatisation@gmail.

com

1. Dispatcher-Performer Architecture: A robot called the Dispatcher uploads tasks into a


queue. These tasks are then processed by one or more Performer robots. This setup helps
balance the workload and allows for easy scaling.

Dispatcher Robot ( Upload Items) Queue Performer Robot(s)


( Process Items)

2. Long Running Workflows Architecture: Tasks are split into smaller parts, each processed
separately. This is helpful for tasks with a lot of waiting time, such as human approval
processes.

Robot ( Add Task Part to Queue) Queue Waiting Time Robot


( Process Task Part) Add Next Task Part to Queue

3. Multi-Stage Processing Architecture: Tasks go through several stages of processing, each


handled by a different robot. This is useful for complex tasks requiring distinct stages.

Robot 1 ( Add Items to Queue 1) Queue 1 Robot 2 ( Process


Items and Add Results to Queue 2) Queue 2 Robot 3 ( Process Results)

4. Priority-Based Processing Architecture: Tasks in the queue have different priorities, and
robots process them based on this. Useful when certain tasks are more urgent than others.

High Priority Item ( Add to Queue) Queue Robot ( Process High


Priority First) Low Priority Item

5. Retry Mechanism Architecture: Failed tasks due to exceptions are automatically retried.
This enhances the robustness of the automation process.

Robot ( Process Item) Exception Retry Queue

6. Parallel Processing Architecture: Multiple robots process different tasks simultaneously


from the same queue, increasing throughput.

Robot 1, Robot 2, Robot 3 ( Process Different Items Simultaneously)


Same Queue

Franck MONGO – UIPATH MVP - IA RPA BPM CONSULTANT – [email protected]


Franck MONGO – UIPATH MVP – IA RPA BPM CONSULTANT – [email protected]

2
7. High Availability Architecture: Multiple Orchestrator instances are set up. If one fails,
others take over, ensuring uninterrupted service.

Orchestrator 1 ( Active) Orchestrator 2 ( Standby) Orchestrator 3


( Standby)

8. Elastic Scalability Architecture: The number of robots changes dynamically based on the
load, helping manage varying workloads over time.

High Load ( Add More Robots) Robots Low Load ( Remove Robots)

9. Distributed Processing Architecture: Processing is divided among several different


machines or locations. Useful for tasks requiring significant computing resources or specific
locations.

Robot Machine 1, Machine 2, Machine 3 ( Process in Different


Machines)

10. Event-Driven Architecture: Robots are triggered to process tasks when certain events
occur, like the arrival of new data.

Event (Trigger) Robot ( Process Queue Items)

11. Failover Architecture: A backup or secondary robot is ready to take over if the primary
robot fails. This helps minimize downtime and ensures continuity of service.

Primary Robot ( Active) Failure Backup Robot ( Take Over)

12. Service-Oriented Architecture (SOA): This architecture is designed around services that
are provided by robots. Each service is a separate function that can be used by other parts of
the system. This is useful when you have tasks that can be broken down into independent
services.

Robot ( Provide Service 1) Robot ( Provide Service 2) Robot (


Provide Service 3)

Franck MONGO – UIPATH MVP - IA RPA BPM CONSULTANT – [email protected]


Franck MONGO – UIPATH MVP – IA RPA BPM CONSULTANT – [email protected]

3
13. Pipeline Architecture: In this architecture, tasks are processed in stages, with the output
of one stage being the input of the next. This is useful for tasks that involve a series of
transformations.

Stage 1 Stage 2 Stage 3 Stage 4

14. Hybrid Architecture: This is a combination of different architectures to suit the specific
needs of a system. This can be beneficial when no single architecture can meet all the
requirements of the system.

( Dispatcher-Performer Architecture Priority-Based Processing Architecture


Retry Mechanism Architecture)

Remember, these are simple explanations and illustrations of these architectures. Real-
world implementations can be much more complex and may involve additional elements
depending on the specific requirements of the system.

Franck MONGO – UIPATH MVP - IA RPA BPM CONSULTANT – [email protected]

You might also like