What is the best approach to fan out data being streamed?
I have a use case were I'd like to fan out data I am getting with EMA to multiple end users (I have a license for this). What are some good ways to do this?
Specifically once challenge I see is that clients streaming data will come and go and the symbols I need to stream will regularly be changing.
For example
Client 1 can come and stream TSLA and IBM
Client 2 comes along and wants TSLA and BMO
Client 3 comes along and wants APPL
Would I need to create seperate stream for each of these connections noting that I will be streaming thousands of symbols to thousands of clients?
Best Answer
-
Thanks for reaching out to us.
Typically, EMA will hande fanout on behalf of the application. Therefore, the code can look like this:
AppClient client1;
AppClient client2;
AppClient client3;
OmmConsumer consumer( OmmConsumerConfig().username( "user" ) );
printf("\n####Subscribe Client 1####\n");
UInt64 handle = consumer.registerClient(ReqMsg().serviceName("ELEKTRON_DD")
.payload(ElementList().addArray(ENAME_BATCH_ITEM_LIST, OmmArray().addAscii("TSLA.O").addAscii("IBM.N").complete()).complete()),
client1);
sleep(10000);
printf("\n####Subscribe Client 2####\n");
handle = consumer.registerClient(ReqMsg().serviceName("ELEKTRON_DD")
.payload(ElementList().addArray(ENAME_BATCH_ITEM_LIST, OmmArray().addAscii("TSLA.O").addAscii("BMO.TO").complete()).complete()),
client2);
sleep(10000);
printf("\n####Subscribe Client 3####\n");
handle = consumer.registerClient(ReqMsg().serviceName("ELEKTRON_DD").name("AAPL.O"),
client3);The application needs to maintain the handles of the subcribed items for each client so the application can unsubscribe items.
Otherwise, you can implement fanout logic in the application by maintaining the application's watchlist.
However, it depends on how you design the application. Using the watchlist and fanout features in EMA is easier.
I hope that this information is of help.
0
Answers
-
Thanks for the response. I had a few follow up questions to this:
1) Is it efficient to register thousands of clients via consumer.registerClient(...) some of which subscribe to the same symbols?
2) Does each call to consumer.registerClient use the same connection to ADS?
3) If the answer to #2 is yes, at what point would a new separate connection be required before single connection can no longer handle the load?
0
Categories
- All Categories
- 6 AHS
- 37 Alpha
- 161 App Studio
- 4 Block Chain
- 4 Bot Platform
- 16 Connected Risk APIs
- 47 Data Fusion
- 30 Data Model Discovery
- 608 Datastream
- 1.3K DSS
- 577 Eikon COM
- 4.9K Eikon Data APIs
- 7 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- Trading API
- 2.7K Elektron
- 1.3K EMA
- 236 ETA
- 519 WebSocket API
- 33 FX Venues
- 10 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 20 Messenger Bot
- 2 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 59 Open Calais
- 264 Open PermID
- 39 Entity Search
- 2 Org ID
- PAM
- PAM - Logging
- 8.4K Private Comments
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 20 RDMS
- 1.4K Refinitiv Data Platform
- 367 Refinitiv Data Platform Libraries
- 3 Refinitiv Due Diligence
- LSEG Due Diligence Portal API
- 3 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.1K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 10 World-Check Customer Risk Screener
- 990 World-Check One
- 44 World-Check One Zero Footprint
- 45 Side by Side Integration API
- Test Space
- 3 Thomson One Smart
- 1.2K TR Internal
- Global Hackathon 2015
- 2 Specialists Who Code
- 10 TR Knowledge Graph
- 150 Transactions
- 142 REDI API
- 1.7K TREP APIs
- 4 CAT
- 21 DACS Station
- 117 Open DACS
- 1.1K RFA
- 103 UPA
- 172 TREP Infrastructure
- 224 TRKD
- 886 TRTH
- 5 Velocity Analytics
- 5 Wealth Management Web Services
- 59 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛