Async and Queue Designer

Status: Planned. Studio does not yet have a queue or topic designer. This page states the design so teams can plan, and lists what exists today.

What it is for

Work that should not block a user or must reach several systems: a new employee should reach HCM, Payroll and Notifications independently, and one slow consumer must not stop the others.

Concepts

Term	Meaning
Queue	messages processed by one consumer at a time
Topic	messages delivered to every subscriber
Producer / Consumer	who writes and who reads
Consumer group	consumers sharing the work of one topic
Message, partition, offset	a unit of work, an ordered lane, a position in it
Dead-letter queue	where messages that keep failing go for inspection
Idempotency	handling the same message twice is safe
Back-pressure	slowing producers when consumers fall behind

Planned design

Create queue or topic; configure producer and consumer; retry policy; dead-letter queue; ordering; scheduling; providers (Kafka, RabbitMQ, AWS SQS, Azure Service Bus, Google Pub/Sub, Redis Streams) behind one interface.

Employee created -> event -> topic -> HCM consumer
                                   -> Payroll consumer
                                   -> Notification consumer

What you can use today

• Asynchronous workflows with human tasks and timers.
• Jobs for scheduled and background work (Jobs).
• Integration Flows with worker execution and retry (Integrations).
• Plugin services may use any messaging library; the platform's own messaging is internal.

Security, testing, deployment, troubleshooting

Planned with the feature: per-queue permissions, tenant-scoped topics, test publish and consume from Studio, region-aware deployment, message trace.

Related

Events, Jobs.