The answer is yes. When we talk about this asynchronous stream outbound from Reltio, which is really the only way that Reltio does support asynchronous on the inbound side, you would turn a streaming event into an API call for Reltio in order for Reltio to be updated. On the outbound side, Reltio currently natively supports AWS SQS, AWS SNS, Google Pub-sub, and Azure Service Bus. And in the context, for example, of something like AWS SQS, then the published event as a type. And that type will be one of a whole plethora of different types that are considered materially interesting to the outside world, like entity changed, entity added, entities matched, merged, unmerged, those kinds of things.
When a message concerns an entity being added or changed, then it will include a representation in that JSON payload of the entity itself in its entirety. If it is simply talking about an entity that merged or was unmerged, it will refer just to the URIs of the underlying entities. And therefore, will not be as complete as you are asking about here.
If you haven't listened to the API-led Integration: Exchanging Data Using Reltio's REST APIs with MuleSoft, take a listen!
------------------------------
Matthew Gagan
------------------------------
Original Message:
Sent: 07-02-2021 08:13
From: Chris Detzel
Subject: When async stream publish events, does it provide event type and entire entity payload being updated/deleted or created?
Any insights on async stream publishing events would be helpful. #API
------------------------------
Chris Detzel
Community Program Manager
Reltio
------------------------------