Reltio data sharing with Databricks - essentials architecture
Learn about the Reltio data sharing with Databricks - essentials architecture and how it shares Delta Lake-formatted data with your Databricks Unity Catalog.
Reltio data sharing with Databricks - essentials automates the infrastructure required to prepare and share Delta Lake-formatted Reltio data with your Databricks Unity Catalog using Open Sharing. The Reltio Databricks architecture provides secure and governed access to trusted Reltio data for analytics, business intelligence, and AI/ML workloads, without requiring customers to move or maintain separate copies of the shared data.
How the Reltio data sharing with Databricks - essentials architecture works
The diagram above illustrates how data flows from the Reltio Context Intelligence Platform to your Databricks environment:
Data Pipeline Service in Reltio: Data from the Reltio Context Intelligence Platform, including entities, relationships, and interactions, is processed by the Data Pipeline Service, which queues, stages, and prepares the data for sharing.
Data sharing with Databricks: The data is transformed into the open Delta Lake table format and securely shared using the sharing identifier provided during data share setup. With Reltio data sharing with Databricks - essentials, data synchronization is triggered every four hours. The time required for updates to become available depends on the volume of data to be processed and the processing duration.
Consumption in Databricks: Once the shared data is available through Unity Catalog, you can use Databricks services and applications to query, analyze, govern, and consume the data for downstream use cases.
End-to-end data sharing with Databricks
With this architecture, your tenant receives Reltio data directly in your own Databricks Unity Catalog. You can use the data for analytics, reporting, and compliance without additional integration work.
To set up a data share, see Configure Reltio data sharing with Databricks - essentials.