Support for routing a response to another pipe

Not planned

Follow

Marius Dammen

• October 23, 2020 11:08

When posting data to a service, it will sometimes return an array with e.g. an id, and a status on the individual record. This result can be merged back (correlated) into the source pipe in Sesam. That way it is possible to take further action on each record based on the result from the post operation. 

This is used when the target api doesn't have GET operations that can support the correlation behavior.

We currently implement this as a feature in microservices, where we push the result to a http pipe (using the sesam api and a token). This works, but it creates a weak link (not visual/tracked) between the system that receives the response and the pipe it is pushed to.

0

• Official comment

  

  Geir Ove Grønmo

  • June 09, 2021 07:58

  This is useful feedback. There has been several parties asking for similar features. We have not yet decided or figured out how to support it. It is not unlikely that the REST sink will get a feature like that at some point, but there are no concrete plans for supporting this yet.

  Comment actions Permalink
• 

  egemen.yavuz

  • June 09, 2021 08:40

  There is a microservice on sesam-community space that cab be used here : rest-transform

  By using this service, "post-and-save-the-response-in-sesam" functionality can be omitted from the target api.

  0

  Comment actions Permalink

Please sign in to leave a comment.