For a deeper look into our Elektron API, look into:
Overview | Quickstart | Documentation | Downloads | Tutorials | Articles
2 NIPs with different latency
I use Elektron and TREP2.6/TREP3.3.
In order to get a fault tolerant infrastructure, I create two NIPs who publish the same data into an ADH pair. The ADH aggregates the two services (NIPSERVICE1 and NIPSERVICE2) into a final service (NIPSERVICE).
These NIPs may have different latency. I'd like to know how to be sure that the ADH cache (NIPSERVICE) contains only the latest data.
Here's an example where I could have an incorrect data in NIPSERVICE
Is there a way to prevent this problem
I just realized that using the service aggregation is probably not how I'm supposed to create a fault tolerant infrastructure...
- Is there a better way to have 2 NIPs, live/live, publishing the same data into an ADH?
- Or should I try to create live/hot standby NIPs?
- Any advice?
Hello @nicolas.roux
Normally Developer Community Forum is for how-to/general questions. However, your question seems to be complex and requires much effort to find out the proper solutions for you from the API support team.
Since you are the premium user who we can support your cases, could you submit a case for these question via this form with the API product name and its edition e.g. RFA C++, RFA Java? Once we receive your case, we can assist you accordingly. If you have any problem to submit the case to us, please send an email to rdc.administrator@thomsonreuters.com