Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Messaging connector for Oracle Queue Service (OQS) #4739

Open
danielkec opened this issue Aug 15, 2022 · 0 comments
Open

Messaging connector for Oracle Queue Service (OQS) #4739

danielkec opened this issue Aug 15, 2022 · 0 comments
Assignees
Labels
enhancement New feature or request messaging Reactive Messaging OCI P2

Comments

@danielkec
Copy link
Contributor

danielkec commented Aug 15, 2022

Implement OCI OQS messaging connector

Oracle Queue Service (OQS): Is a new multi-tenant and highly available queuing service to handle application decoupling, reliable message processing, and handling scale bursts. Queue service removes the burden of operating and managing complex middleware products so developers can focus on building the business logic. This product is designed and built with the vision to allow customers to send, store, and receive messages at scale within sub-second latency and best-effort ordering guarantees. Queue service provides message-level delivery guarantee and failure handling. Queue service scales elastically based on application load, so developers won’t have to worry about capacity planning and pre-provisioning.

@danielkec danielkec added enhancement New feature or request messaging Reactive Messaging OCI labels Aug 15, 2022
@barchetta barchetta added the P2 label Aug 18, 2022
@trentjeff trentjeff mentioned this issue Oct 4, 2023
1 task
@m0mus m0mus added this to Backlog Aug 12, 2024
@m0mus m0mus moved this to High priority in Backlog Aug 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request messaging Reactive Messaging OCI P2
Projects
Status: High priority
Development

No branches or pull requests

2 participants