Reltio Connect

Hi Team,

Can you please let me know the pros and cons of sharing the Reltio default API endpoints with the downstream systems or consuming systems ?

Should  we allow them to use the Reltio default GET API's on entities and entity relationships so they can apply the filters as necessary and fetch the required data or is it advised to create custom API's using RIH and expose only the attributes that are required for the downstreams ?

I understand it completely depends on the use case but would like to know the best practices around this.

Hi Sridhar,

As a standard practice, we do not directly expose the tool's endpoints to upstream or downstream. We should introduce a middleware tool in between. Here are a few reasons why you shouldn't do it:

1. Manage complexity: Different tools have different sets of data, constraints, and limitations. If you try to handle this in MDM tool then it might make your solution more complex. 
2. Hiding the complexity and changes: The endpoint of the Reltio tool might change over time. This will affect all sources/targets using the endpoint. If there is a later in between that can absorb these changes and make the Reltio API endpoint opaque to source/target.
3. Make the endpoint consistent with the enterprise requirement: Most enterprises have set of guiding principle which defines the endpoint properties and behavior. Introducing Middleware can solve the problem.
4. Consistent canonical structure for endpoints
5. Security: Sources/Targets need not know about the behavior, limitations, and vulnerabilities of the Reltio tool. Hide it behind a wall (Middleware).
6. User Management: If you let source/target access API directly then you need to create the respective user and manage access per source/target.

Reasons you might want to expose Reltio endpoint:

1. Quick POC
2. Only 1-2 sources and targets in scope and enhancements/changes are required.

Thanks

Gaurav

Ex-Informatica

Ex-Deloitte

https://www.linkedin.com/in/gaurav-ips-infa

Hi Team,

Can you please let me know the pros and cons of sharing the Reltio default API endpoints with the downstream systems or consuming systems ?

Should  we allow them to use the Reltio default GET API's on entities and entity relationships so they can apply the filters as necessary and fetch the required data or is it advised to create custom API's using RIH and expose only the attributes that are required for the downstreams ?

I understand it completely depends on the use case but would like to know the best practices around this.