Migrate API RFA a EMA

jose.barraza

I am using Net RFA 8 NET150, and I want to migrate this solution to a newer technology since I was told that RFA Net is becoming obsolete. What do you suggest to generate subscriptions and continue receiving real-time information? I was told that the ETA solution might be ideal.Where can I find documentation and implementation examples? Regards

wasin.w

Hello @jose.barraza

There is the Enterprise Message API (EMA) C# edition that might suit your need. This message-level API is part of the Real-Time SDK (RTSDK) C# edition (EMA + ETA APIs). You can find the API resources such as Quick Start, Document, SDK package download, step-by-step tutorials from the SDK https://developers.lseg.com/en/api-catalog/real-time-opnsrc/rt-sdk-csharp page.

The implementation example is available in the SDK package and https://github.com/Refinitiv/Real-Time-SDK .

The other resources that might help you are as follows:

• Choosing a Real-time Streaming API article.
• Migrating from the Legacy Robust Foundation API (RFA) to the Enterprise Message API (EMA) article.

jose.barraza

Thank you very much for your response. Another question:

Regarding RFA (Reuters Financial Adapter) for .NET Framework, we've consistently experienced performance issues with subscriptions, as it doesn't efficiently handle a large number of them. Specifically, as the number of RICs (Reuters Instrument Codes) we subscribed to increased, starting around 5000, we encountered performance degradation, including delays in receiving responses. Do you know the limit on the number of instrument subscriptions that can be reliably listened to or processed without significant performance impact?

Jirapongse

@jose.barraza

RFA in this context is LSEG Robust Foundation API.

Typically, there is no limit on the number of instrument subscriptions in RFA. The performance depends on how fast the application can process events dispatched from event queues.

The problem that you encountered could be a slow consumer. For more informantion, please refer to the following discussions.

• Latency problem of Update Message
• Observed overflow in the RFA Query

jose.barraza

"Ok, thank you very much. What example should I follow to develop a service that continuously listens to events from different instruments or RICs, and at the same time allows me to subscribe to multiple RICs as well as define which FIDs to expect from Refinitiv? I don't want all the FIDs for the instruments, just specific ones. Thank you very much, I look forward to your response. Best regards."

Jirapongse

https://community.developers.refinitiv.com/discussion/comment/123628#Comment_123628

@jose.barraza

The example for view requests is in the Examples\StarterConsumer_BatchView directory and the performance application is in the PerfTools\rfanetConsPerf directory.

wasin.w

https://community.developers.refinitiv.com/discussion/comment/123628#Comment_123628

Hello @jose.barraza

The equivalent examples for the EMA C# are:

• 360_MP_View (request only specific FIDs)
• 370_MP_Batch (request multiple RICs in the same request)

The examples are available in the RTSDK C# package as well.

The EMA Batch and View can be combined together (the same as RFA). For more detail, please check the Enterprise Messaging API (Java) - Batch and View features article. The article describes with EMA Java, but you can apply the same concept with EMA C# easily as the API interfaces are almost identical.

jose.barraza

Thank you very much for your help. I’m new to EMA or ETA integration, and the general idea of the project is to subscribe to more than 10,000 RICs and listen to 8 FIDs for each of them. Then, we plan to store this data in a database to expose these values to different business applications through web services (APIs).

This is why the choice between EMA or ETA is crucial in terms of performance and latency, while also meeting the requirement to track updates and movements of these FIDs during financial market hours. Another key point is that the service will be listening for approximately 8 hours a day, constantly storing updates in our tables.

Any suggestions to help us carry out this project are welcome. Thank you once again!

Jirapongse

https://community.developers.refinitiv.com/discussion/comment/123644#Comment_123644

ETA provides the highest performance while EMA is ease of use and provides high performance.

The performance of the application can be determined by measuring the number of update messages that the application can handle per second.

You can check the Real-Time SDKs Performance Test Summary article regarding the performance of Real-Time C/C++ and Java APIs. We don't have a performance report for Real-Time SDK C#.