Build OCI Queue service configurations with dead letter queues and channel settings.
Last verified: May 2026
Build OCI Queue service configurations with dead letter queues, channels, and visibility settings.
Required Fields
compartmentIddisplayNameretentionInSecondsvisibilityInSecondsOutput will appear here...OCI Queue is a fully managed message queuing service that decouples producers and consumers in distributed applications. It provides at-least-once delivery, configurable visibility timeouts, dead-letter queues, and long polling for efficient message consumption. This builder helps you configure queues with retention periods, visibility timeout settings, dead-letter queue policies, maximum message sizes, and channel configurations for multi-consumer patterns.
Your team's order processing has been losing 0.5% of orders to silent failures. Investigation reveals their SQS-equivalent queue had no DLQ and a 30-second visibility timeout, but the order processor sometimes takes 45 seconds — messages reappear, processor sees a 'duplicate', second processing fails, eventually deleted. The builder generates: 90-second visibility timeout, DLQ with maxReceiveCount=3. After deploy, lost orders drop to ~0% and the DLQ surfaces 5-10 messages/week worth investigating instead of silently disappearing.
Long polling (waitTimeSeconds=20) eliminates the 'consumer constantly polling empty queue' anti-pattern. Without long polling, a Lambda/Function consumer might invoke 100K times/day just to find empty queues. Long polling waits up to 20 seconds for messages, dramatically reducing API call costs.
ALWAYS configure a dead-letter queue (DLQ) for production queues. Without DLQ, messages that fail repeatedly are silently dropped after retention expires — you lose visibility into failure patterns. Set max receive count to 3-5 attempts, then DLQ for inspection and replay.
Visibility timeout should match your consumer's expected processing time + safety margin. Too short = duplicate processing as messages reappear. Too long = slow recovery from consumer crashes. Start at 2x your p95 processing time, tune based on actual behavior.
The builder constructs OCI Queue configurations: queue resource (display name, compartment, retention seconds, visibility timeout, dead-letter queue policy with maxReceiveCount, channel configuration). For multi-consumer patterns, separate channels per consumer group. Output is generated as oci queue commands and Terraform oci_queue_queue resources, plus a separate DLQ resource if configured.
Was this tool helpful?
Disclaimer: This tool runs entirely in your browser. No data is sent to our servers. Always verify outputs before using them in production. AWS, Azure, and GCP are trademarks of their respective owners.