Oracle Cloud Infrastructure (OCI) Queue is a fully managed, serverless messaging service designed for asynchronous communication between distributed systems. It handles high-volume transactional data that requires independent processing while ensuring no message loss or duplication. Built on open standards like STOMP and REST APIs, OCI Queue makes it easy to integrate with any client application.
OCI Queue enables true service independence through asynchronous connectivity. Components can scale independently, and your architecture remains flexible as new services can seamlessly publish or subscribe to queues without disrupting existing workflows.
The service transparently handles traffic spikes and varying demand patterns. It can ingest massive message volumes during peak periods while allowing consumers to process messages at their own pace with limited resources.
Integration is straightforward thanks to support for RESTful APIs (with OpenAPI specifications) and the industry-standard STOMP protocol, reducing development time and complexity.
Messages persist until explicitly deleted or expired, with at-least-once delivery guaranteed. The service also provides fair message distribution across channels, protecting against resource monopolization by individual consumers.
Creating a queue is straightforward through the OCI Console:
Publishing is simple via REST API:
Messages can be published to the main queue or specific channels within it. Channels are ephemeral destinations that provide additional organization and fairness in message distribution.
Retrieve messages using the GET endpoint:
Each response includes up to 20 messages with their payload, message ID, expiration time, delivery count, and receipt. The receipt is crucial for updating or deleting messages. The service supports long polling for efficient consumption patterns.
OCI Queue integrates seamlessly with Oracle Integration Cloud (OIC). One integration can publish messages to a queue using the OCI Queue adapter, while another integration subscribes and processes those messages independently. This pattern enables:
Dead letter queues are automatically created with every queue to handle problematic messages. When a message exceeds the maximum delivery attempts (due to processing failures or visibility timeout expirations), it's automatically moved to the dead letter queue. This allows you to:
Messages in dead letter queues remain until their retention period expires, giving you time to analyze and address issues.
OCI Queue provides comprehensive APIs for complete queue lifecycle management:
When you delete a queue, all associated resources are removed automatically, including all messages, channels, and the dead letter queue. This ensures clean resource management without orphaned data.
OCI Queue offers a powerful, fully managed solution for building resilient, scalable distributed systems. Its support for open standards, automatic scaling, reliable delivery guarantees, and seamless integration with Oracle's ecosystem makes it an excellent choice for modern cloud-native applications. Whether you're building microservices architectures, event-driven workflows, or integration platforms, OCI Queue provides the foundation for reliable asynchronous communication.
Back to All Blogs