The UiPath architecture is made up of three layers, INCLUDING:

Client LAYER: This layer COMPRISES UiPath components that users can interact with. UiPath Studio, UiPath Agent, Robots, Browsers, and Executors are some of the examples. These components can be used to build and develop AUTOMATION tasks. UiPath bots then carry out the tasks that have been created. The layer is sometimes referred to as the presentation layer.

Server Layer: This layer displays all of the server-related information. The UiPath Orchestrator is located on this tier. The full project is published to the server once the UiPath bots have been constructed and can execute tasks without issues. The project can be easily executed on several platforms thanks to an Orchestrator. The Orchestrator is in charge of the entire project and assists us in MEETING service levels and schedules.

Persistence Layer: Database servers make up the majority of the persistency layer. The layer is used to hold UiPath bot configuration information. It also organizes and regulates queues, as well as the tasks currently in them.
Data from different users, logging information, associated robots, assigned tasks, asset details, and so on are all included in the configuration details. Users often enter the needed details in the Orchestrator.