> For the complete documentation index, see [llms.txt](https://stephen-tsoi.gitbook.io/stephen-tsoi-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://stephen-tsoi.gitbook.io/stephen-tsoi-docs/messaging-technology/messaging-bus-comparison-series/comparision-7-delay-queue.md). # Comparision #7: Delay Queue #### Research Progress 🟩 Completed: 7 / 20 ✅ #1 Push vs Pull ✅ #2 Point-to-Point vs Pub/Sub ✅ #3 Persistent vs Non-Persistent Connection ✅ #4 Persistent vs Non-Persistent Deliver ✅ #5 Temp Queue ✅ #6 Non-Persistent vs Direct Message ✅ #7 Delay Queue Upcoming: ⏭️ #8 DLQ Queue ⏭️ #9 DLQ LVQ ⏭️ #10 Support Protocols


Product	Supports Delay Queue (Y/N)	Delay Value Range	Margin of Error	Level
ActiveMQ	Y	No fixed limit	±1	Message-level
AWS SQS Queue	Y	0s to 900s	Not documented	Message-level, Queue-level
Azure Queue Storage	N
Azure Service Bus	Y	0 - 15 minute Amazon SQS 延遲佇列	Not documented	Message-level Queue-level
EMQX	Y	Up to 42,949,669s	Not documented	Topic-level
IBM MQ	Y	No fixed limit	Not documented	Message-level
Kafka	N
RabbitMQ	Y, via RabbitMQ Delayed Message Plug-in	268,435,455s	±1	Message-level
Solace PubSub+	Y	0s to 4,294,967,295s	±1	Message-level, Queue-level
Tibco EMS	Y	No fixed limit	Not documented	Message-level

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://stephen-tsoi.gitbook.io/stephen-tsoi-docs/messaging-technology/messaging-bus-comparison-series/comparision-7-delay-queue.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.