- Getting started
- Licensing
- Setup and configuration
- Using the service
- Reference
- Examples and tutorials
Data Fabric user guide
Hosting model
Data Fabric is built using the best practices for cloud services and has been architected to support multiple customers. The service is designed to ensure full isolation of data between different tenants and accounts while providing instantaneous provisioning, deployment, and scale.
When you enable Data Fabric for your tenant, a new partition is created in the service to host your metadata and data. Note that Data Fabric is a tenant level service and each tenant has their data segregated. All subsequent operations for that tenant are then restricted to its respective partition. Additionally, all communication with the service happens via REST APIs.
Data Fabric is built on top of UiPath® Automation Cloud and has the following main components:
- Web Application - Provides the user experience for Data Fabric.
- Rest API Endpoints - Consumed by Web Application, Studio, and Robot for all operations.
- Runtime + Storage Management Service - Responsible for ensuring partitioned access and operations to modify entities and records in Metadata or Data stores.
- Metadata Store - Stores information about entities, fields, users, and permissions for each tenant.
-
Data Store - Stores the records for each entity.
UiPath® Studio, Assistant and Robot communicate with Data Fabric using their configured Orchestrator connection, they are able to both identify the Data Fabric endpoint and obtain authentication tokens from Automation Cloud. Operations like importing entities in Studio read the metadata about entities from Data Fabric and then store it with the Project. Data Fabric activities communicate with REST API endpoints to read or modify records.
