A queue system whose subscribers can listen for messages, rather than poll periodically.
A queue system whose subscribers can listen for messages, rather than poll periodically. An implementation of a push queue is IronMQ, as announced on their blog.
A non-push queue expects subscribers to simply poll at regular intervals. This works for consistently-busy queues, but for queues that have long periods of low activity, polling slowly wastes time and network bandwidth, essentially doing nothing.
Queue subscriber message fetch styles:
- Listen for message (push queue)
- Wastes zero API requests
- Requires that network circumstances allow the queue service to contact the subscriber
- Poll every second
- Wastes up to 86,400 API requests daily
- Long-poll, with 30 second timeout
- Wastes up to 2880 API requests daily