How does OCI Queue differ from OCI Streaming?

OCI Queue is a traditional message queue (like SQS) designed for point-to-point message delivery with at-least-once semantics — once a consumer processes and deletes a message, it is gone. OCI Streaming is an event streaming platform (like Kafka) where messages persist for a retention period and multiple consumers can independently read the same messages. Use Queue for task distribution and async processing; use Streaming for event streaming, fan-out, and replay scenarios.

What happens when a message exceeds the maximum delivery attempts?

When a message exceeds the configured maximum delivery attempts (each time the visibility timeout expires without the message being deleted counts as an attempt), it is automatically moved to the associated dead-letter queue (DLQ). Messages in the DLQ can be inspected, analyzed for failure patterns, and replayed back to the original queue after fixing the underlying issue. If no DLQ is configured, messages are eventually deleted after the retention period expires.

OCI Queue Config Builder

ServerlessOCI

Build OCI Queue service configurations with dead letter queues and channel settings.

OCI Queue Configuration

Build OCI Queue service configurations with dead letter queues, channels, and visibility settings.

Required Fields

compartmentIddisplayNameretentionInSecondsvisibilityInSeconds

{
  "compartmentId": "ocid1.compartment.oc1..aaaaaaaexample",
  "displayName": "order-processing-queue",
  "retentionInSeconds": 604800,
  "visibilityInSeconds": 60,
  "timeoutInSeconds": 30,
  "channelConsumptionLimit": 10,
  "deadLetterQueueDeliveryCount": 5,
  "customEncryptionKeyId": "ocid1.key.oc1.iad.aaaaaaaexample",
  "purgingConfiguration": {
    "purgeType": "NORMAL",
    "retentionDuration": "PT168H"
  },
  "exampleMessages": [
    {
      "content": "{\"orderId\": \"ORD-12345\", \"action\": \"process\", \"timestamp\": \"2024-01-15T10:30:00Z\"}",
      "metadata": {
        "customHeaders": {
          "priority": "high",
          "source": "web-checkout"
        }
      }
    }
  ],
  "channelDetails": [
    {
      "channelId": "channel-worker-1",
      "consumptionLimit": 5,
      "description": "Primary order processor"
    },
    {
      "channelId": "channel-worker-2",
      "consumptionLimit": 5,
      "description": "Secondary order processor"
    }
  ],
  "deadLetterQueue": {
    "displayName": "order-processing-dlq",
    "retentionInSeconds": 1209600,
    "maxDeliveryAttempts": 5
  },
  "freeformTags": {
    "application": "order-system",
    "environment": "production"
  }
}

Generated Output

Output will appear here...

About This Tool

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.

When to Use This Tool

•Configuring a queue for an order processing system with a 30-second visibility timeout and 5-retry dead-letter queue policy
•Building a queue configuration for async task processing with long polling (20-second wait) to reduce empty response costs
•Setting up a dead-letter queue that captures failed messages after 3 delivery attempts for manual investigation and replay
•Creating a queue with multiple channels to partition messages by priority level for different consumer processing speeds

Frequently Asked Questions

How does OCI Queue differ from OCI Streaming?: OCI Queue is a traditional message queue (like SQS) designed for point-to-point message delivery with at-least-once semantics — once a consumer processes and deletes a message, it is gone. OCI Streaming is an event streaming platform (like Kafka) where messages persist for a retention period and multiple consumers can independently read the same messages. Use Queue for task distribution and async processing; use Streaming for event streaming, fan-out, and replay scenarios.
What happens when a message exceeds the maximum delivery attempts?: When a message exceeds the configured maximum delivery attempts (each time the visibility timeout expires without the message being deleted counts as an attempt), it is automatically moved to the associated dead-letter queue (DLQ). Messages in the DLQ can be inspected, analyzed for failure patterns, and replayed back to the original queue after fixing the underlying issue. If no DLQ is configured, messages are eventually deleted after the retention period expires.

Related Learning Guides

OCI Streaming & Events22 min read

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.