Cloud Queues FAQ
Last updated on: 2016-05-02
Authored by: Megan Meza
Yes. Cloud Queues will offer both public and snet IP’s, so as long as the dedicated network partition is set up to allow traffic to one of these targets, Cloud Queues can be accessed.
Messages can’t get stuck in a queue. After posting a message, the client will receive a resource URL which can be used to delete the message. Alternatively, the client can simply wait for the message to expire, at which point the service will automatically remove it. All messages have a “Time to Live” or TTL, which is configurable by the user.
Each queue is associated with a single cloud account, and is not tied to any server in particular under that account. Queues cannot be migrated between cloud accounts.
Yes, messages cannot be larger than 256K (excluding white space), and a single request cannot contain more than 10 messages. If a single request has multiple messages, the sum of those messages (excluding white space) cannot exceed 256K.
Cloud Queues is based on the OpenStack “Marconi” project and uses its own persistent, highly-available, document-based data store. Cloud Queues is not a wrapper around AMQP or other protocols.
Each message is replicated across three storage nodes, in memory, and also persisted to disk. Messages are not replicated across data centers (regions) at this time.
Cloud Queues offers a simpler, HTTP-based API making it ideal for modern web application development. The service does not rely on, or even support persistent connections other than standard HTTP keep-alive, and so is more reliable when accessed through firewalls and across multiple network partitions (i.e., the Internet). The service is HA and durable, and requires absolutely no setup or maintenance on the part of the developer or system administrator.
We currently only offer a few very basic per-queue stats but intend to develop additional stats for GA The stats currently offered include oldest message, newest message, number of claimed messages, number of unclaimed messages. However, it is easy to hook Graphite up to the
GetQueueStats call to plot graphs on the amount of free and unclaimed messages.
14 days. The default message TTL will be set to 72 hours.
There are no limits on the number of queues or the number of messages that a queue can contain.
Yes, customers will be limited to 300 request per second per account. Please contact support if you need to exceed this limit.
Project ID is the Tenant ID, and is the customer’s account number.
Experience what Rackspace has to offer.
©2020 Rackspace US, Inc.
Except where otherwise noted, content on this site is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License