Talend ESB Mediation best practice

[Peter_Mitchell]

Hello Community.

We are investigating using Talend routes as a mediation platform between two different systems of records. We are looking to set up two-way communications between the two systems by implementing incoming and outgoing APIs and integrating them with webhooks from the systems. One of our systems of record is on-prem (the other cloud-based) and is subject to planned downtime for patching. We are planning on using an ActiveMQ instance for brokering messages between the two endpoints, allowing us to use queueing to cater for the potential downtime of the on-prem system. 

Currently have a test route that carries out the following:

1. Receives incoming REST call
2. Strips URL path parameters from the incoming call using cProcessor
3. Takes stripped parameters and manipulates them into outgoing call's API format using cProcessor
4. Passes outgoing message to ActiveMQ instance through a cMQTT component.
5. Message is then sent to outgoing API and HTTP response code is logged.

 

cProcessor manipulation where x is initialised as the incoming query string of our API and is manipulated for the outgoing system. (Please note, this is just a work in progress and we plan to implement a much more robust way of extracting the incoming URL parameters once we progress with this testing):

 

My question to you is, is this the best design practice for fulfilling this scenario? Are there any other ways that you would go about carrying this out, please?

Thank you and I appreciate all your time reading this post!