Reltio DTSS components
Learn about Reltio DTSS' design and components.
What are the components of Reltio DTSS?
The Data Tenant, Customer Tenant, DTSS event queue, the Application service and the Data Tenant Subscription make up DTSS.
- Data Tenant: A Data Tenant (DT) contains third party data that can be used to enhance the customer’s own data. Data tenants are maintained by Reltio or an Original Equipment Manufacturer (OEM) partner or customers themselves. Access to them can be licensed from Reltio or a third party data partner.
A data tenant can be subscribed to by one or more customer tenants. Custom data tenants can also be created for customers and partners.
- Customer Tenant: Every time a customer licenses Reltio, they get three customer tenants by default to store their customer data, and their business rules: Development, Test, and Production. A customer tenant can subscribe to one or more data tenants containing third party data and all of that third party data can be used to enhance the customer’s own data.
- DTSS Event Queue: When any change occurs in a data tenant, an event is published onto an internal queue with the ID of the record that created the event as well as the event type.
- DTSS Application Service: The DTSS event queue is monitored by the DTSS application service which evaluates each event and takes action in accordance with the business rules defined in the subscription for each customer tenant.
- Data Tenant Subscription: When a customer licenses a Reltio DTSS service, Reltio will create an initial subscription between the DT and the CT. A variety of operations for accessing, monitoring, and administering are available to customers via the application service API.
The data tenant subscription is a set of configurable rules that enable you to define how data can be moved from a DT to a CT. The definition of the subscription is held in a JSON file.