Architecture overview

Reltio Zero Copy Interaction Integration from Databricks architecture connects Reltio to Databricks through a configured Databricks connection, an interaction mapping, and OAuth 2.0 machine-to-machine authentication with a Databricks service principal. Together, these components let Reltio identify the Databricks source to query, retrieve the required interaction data, and return it for the related profile in Intelligent 360.

The following diagram illustrates how Reltio connects to Databricks to retrieve interaction data and return it in the context of unified profiles.

Reltio Zero Copy Interaction Integration from Databricks architecture includes the following main elements:

• Reltio Intelligent 360, which requests and returns interaction data in the context of the related profiles.
• Databricks Warehouse, which executes queries against the mapped Databricks source.
• Databricks tables or views, which store the interaction and transaction data used by the integration.
• An interaction mapping, which defines the Databricks source, returned attributes, interaction type, and profile linking rules.
• A Databricks service principal, which provides OAuth 2.0 machine-to-machine authentication for the connection.

Databricks query flow and profile linking

Reltio uses the configured interaction mapping to determine which Databricks table or view to query and which source columns to return as interaction attributes. Databricks executes the query in SQL Warehouse and returns only the matching rows for the request. Reltio then returns that interaction data in the context of the related profiles.

Profile linking depends on the crosswalk values stored in the Databricks source. Each mapped source must include a column that contains the crosswalk ID used to associate the Databricks interaction row with the correct Reltio entity. The mapping also defines the interaction type, the timestamp column, the sort column, and the attributes that Reltio returns from the Databricks source.

Databricks source objects are referenced by using the Unity Catalog three-part name in the catalog.schema.table format. This lets Reltio identify the mapped object in the Databricks catalog structure.

Authentication and access control

Reltio Zero Copy Interaction Integration from Databricks architecture uses OAuth 2.0 machine-to-machine authentication with a Databricks service principal. OAuth 2.0 machine-to-machine authentication lets Reltio authenticate to Databricks by using a service principal instead of a user sign-in. After the service principal credentials are stored in Reltio, Reltio uses them to request access tokens from Databricks and refreshes those tokens as needed for the connection. Personal Access Tokens are not supported for this integration.

Reltio accesses only the Databricks SQL Warehouse and Unity Catalog objects that the configured service principal is allowed to use. This means Databricks continues to control access to the external interaction data, while Reltio queries that data only for the mapped integration flow.

What this architecture enables

Reltio Zero Copy Interaction Integration from Databricks architecture lets Intelligent 360 combine mastered profile data in Reltio with interaction data that remains in Databricks. As a result, you can use a unified view that includes external interaction data without creating a replicated interaction store in Reltio.