Reltio Connect

This will avoid calling back Reltio for full payload, also, what happens when the payload size is greater than 256KB? As we know SQS has limitation of 256KB

The answer is yes; we can do that today. This is a new functionality that is being released, that just got released. We can trigger, and you can specify as part of queue definition what attributes you would like to be published to that message. You can write all your attributes, or you could even filter some of them if you only want a few of them in that object to be shared downstream. And we just touched on if the payload is larger than 256, we still only publish the URI and the event, and then we publish in an error code inside of that message so that your reader can then go make that get callback URL to get that full object.

We expect those to be few and far between for most of our customers that the large majority of our objects will fall underneath that size limit. It should reduce the overall API interactions that you need to go through to process this data downstream.

This is an exciting thing I think for a lot of our customers that have moved to real time where they have a significant amount of API overhead in just making those get calls back to Reltio.

When the payload size is greater than 256kb, what happens is we write a message out that has an error code in it for that reader, that listener to then make an API call back to Reltio to get the full object. You will still get the event, you will still get the ID for that event, we just will not publish the full payload of that event. We will publish an error code that you know you need to go make that call back to Reltio.

If you missed the webinar around Data Extraction, here it is below: