RabbitMQ integration¶
If you are not our client, you can request temporary access to the demo RabbitMQ for additional analysis. Please provide your corporate IP address for access whitelisting.
Consumer configuration¶
Do not use auto-ack mode
We cannot guarantee RabbitMQ stability if auto-ack is used. When auto-ack is enabled, all pending messages in a queue are loaded into the broker's RAM. This can lead to Out-of-Memory (OOM) kills on the broker side if there is a large message backlog. Any in-flight messages consumed with auto-ack and awaiting delivery will be lost in the event of a failure.
Use manual-ack with prefetchCount
You must use manual-ack with a reasonable prefetchCount value. This combination limits how many unacknowledged messages are held in the broker's RAM, keeping its memory usage under control.
Available queues¶
| Queue | Description |
|---|---|
| markets-queue | Snapshots with markets by event |
| market-results-queue | Snapshots with market results by event |
| events-queue | Information about events |
| scores-queue | Information about scores by event |
| categories-queue | Information about categories |
| tournaments-queue | Information about tournaments |
| sports-queue | Information about sports |
| event-free-form-templates-queue | Information about free forms |
| line-items-dependency-pairs-queue | Information about dependecy pairs |
| bet-returns-queue | Information about returns |
| bet-rejected-queue | Information about returns |
| bet-blocked-queue | Information about returns |