.NET Refinitiv Data - AWS queue configurability

Hi, we are using this example https://github.com/LSEG-API-Samples/Example.DataLibrary.DotNet/blob/main/src/3.%20Delivery/3.3-Queue/3.3.02-Queue-NewsStories/3.3.02-Queue-NewsStories.cs to create queues for messages.
I was wondering how much control we have over the queue and its behavior, e.g. is there a way of acknowledging a message that we have processed? I cannot see any interface for that in the library.
Best Answer
-
Hi @lukasz.druczak,
There are no AWS examples in .Net that was created - I basically followed documentation/examples to work with queues I created using the RDP endpoints and utilized the AWS libraries to extract messages from the queues.
The Message Queue URLs provide the details to retrieve, create and delete queues within AWS. For example:
And when you create a queue, you are given details like this:
From here, I would begin to utilize the AWS libraries to pull down details from the queues. I do nothing special to queues as I don't control the configuration of them.
In general, when you create a queue you simply pull off messages at your leisure. However, as expected, there will be some sort of limit as to the number of messages can exist in the queue before the old ones are removed in favor of more recent ones.
Regarding details like:
"How is the queue configured"?
"How many messages does it keep"?
"How long does it live"
Are not managed or configured by the library. These are policies entirely managed by the platform. If you need these level of details, the best resource is to open a helpdesk ticket and they will bring in a backend person to provide these details.
If you want to work with the library and the message queues yourself, you can certainly do this. For example, you can utilize the delivery layer that provides the mechanism to work with the message queue endpoints. What this will do is allow you to: create, retrieve and delete queues within AWS using the EndpointRequest.Definition(). For example, you can retrieve a queue using one of the endpoints and when you have the queue details returned to you, you can begin using the AWS libraries to retrieve messages from the queue. Note: this is a rather ambitious approach and I would recommend you figure out exactly why you need to do this. It's unclear to me what additional details/configuration you need to perform given you have no control over how queues are created in the backend.
0
Answers
-
There is no direct control of the underlying queue - unless you choose to use Amazons Queue Libraries (AWSSDK.Core, AWSSDK.SQS) directly.
Regarding message acknowledgement, what the library does is delete the message from the queue. In Amazon SQS, acknowledging a message is done by deleting the message.
Hope this helps.
0 -
Hi @nick.zincone, thank you for your prompt answer.
Can you shed some more light on how the underlying queue is configured? If we create a queue and do not delete it - how long does it live? Ho much messages can it keep?
Regarding the Amazons Queue Libraries - how can we make use of them together with RDP? Do you maybe have an example of such solution?
0 -
Hi, @nick.zincone
Have you had a chance to look at my query?
0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 690 Datastream
- 1.4K DSS
- 629 Eikon COM
- 5.2K Eikon Data APIs
- 11 Electronic Trading
- 1 Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 255 ETA
- 559 WebSocket API
- 39 FX Venues
- 15 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 25 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 279 Open PermID
- 45 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 23 RDMS
- 2K Refinitiv Data Platform
- 716 Refinitiv Data Platform Libraries
- 4 LSEG Due Diligence
- LSEG Due Diligence Portal API
- 4 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.2K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 12 World-Check Customer Risk Screener
- 1K World-Check One
- 46 World-Check One Zero Footprint
- 45 Side by Side Integration API
- 2 Test Space
- 3 Thomson One Smart
- 10 TR Knowledge Graph
- 151 Transactions
- 143 REDI API
- 1.8K TREP APIs
- 4 CAT
- 27 DACS Station
- 121 Open DACS
- 1.1K RFA
- 106 UPA
- 194 TREP Infrastructure
- 229 TRKD
- 918 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 95 Workspace SDK
- 11 Element Framework
- 5 Grid
- 19 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛