|
In my org, we are planning on using a delayed message for scheduled push notification. Is there a storage cost, and how does it affect the cloud instance and pricing. What are the storage limit? |
Replies: 1 comment
|
Yes, there is storage cost. Delayed messages are retained in an internal delayed queue until they are due, so they occupy broker storage while they are waiting. In the source, delayed exchange messages are pushed to a delayed message store, written to disk, and indexed in memory by expiration time so they can be routed later. Durable delayed exchanges persist across restart; non-durable/transient behavior follows the usual transient queue rules. For sizing, treat it as roughly the payloads and message metadata for all outstanding scheduled notifications, plus segment/index overhead. A very long scheduling horizon can therefore accumulate a real backlog. CloudAMQP pricing and hard limits are plan/quota-specific, so the exact disk limit needs to come from your plan documentation or CloudAMQP support. |
Yes, there is storage cost. Delayed messages are retained in an internal delayed queue until they are due, so they occupy broker storage while they are waiting.
In the source, delayed exchange messages are pushed to a delayed message store, written to disk, and indexed in memory by expiration time so they can be routed later. Durable delayed exchanges persist across restart; non-durable/transient behavior follows the usual transient queue rules.
For sizing, treat it as roughly the payloads and message metadata for all outstanding scheduled notifications, plus segment/index overhead. A very long scheduling horizon can therefore accumulate a real backlog. CloudAMQP pricing and hard limits a…