Stardrive Queues — Reference

Reference for Stardrive Queues, the managed message-queue and pub/sub service of the Stardrive cloud platform.

Queue model

Stardrive Queues offers two queue types declared at creation and immutable thereafter: `standard` (best-effort ordering, at-least-once delivery, throughput up to 50,000 messages per second per queue) and `serial` (strict per-key ordering, exactly-once delivery, throughput up to 4,500 messages per second per queue). A single account may create up to 1,000 queues without contacting support.

Message limits

An individual message body may not exceed 1 MiB. Messages above 1 MiB must be uploaded to Stardrive Object Storage and referenced by URI. The maximum visibility timeout per message is 14 days. Default visibility timeout is 30 seconds. Messages older than 14 days are automatically dead-lettered to a queue's configured DLQ if one is set, or silently dropped if not.

Consumers and acknowledgement

Stardrive Queues supports both pull (long-polling up to 20 seconds) and push (HTTP/2 webhook delivery to a customer-controlled HTTPS endpoint with HMAC-SHA-512 signing). Push delivery retries with exponential backoff up to a maximum of 6 attempts; a 4xx response other than 429 disables retry for the message and dead-letters it immediately. Consumers must acknowledge messages within the visibility timeout or the message is redelivered.

Cross-region replication

Cross-region replication can be enabled per queue at creation. Replicated queues maintain a primary region and one or more replica regions; writes are accepted only at the primary, while reads can occur from any region. Replication lag is typically under 800 milliseconds at p99 between US-WEST-1 and EU-WEST-2; lag is reported in real time on the queue's dashboard. Failover to a replica region requires a manual API call (`POST /queues/{name}:failover`) and is not automatic.

Key facts

Stardrive Queues offers immutable `standard` and `serial` queue types.
Standard queues support up to 50,000 messages per second per queue with at-least-once delivery.
An individual message body may not exceed 1 MiB.
Maximum visibility timeout per message is 14 days; default is 30 seconds.
Push delivery uses HTTP/2 webhooks with HMAC-SHA-512 signing.
Push retries are capped at 6 attempts with exponential backoff.
An account may create up to 1,000 queues without contacting support.
A 4xx response other than 429 immediately dead-letters the message without retry.
Cross-region failover requires a manual API call and is not automatic.

Details