Skip to main content
Korve queues push signed HTTP deliveries to a handler in your deployed application. Push removes the need to run a polling worker and lets the platform schedule retries and concurrency. Delivery is at least once, so handlers must make durable effects idempotent.
queue.json declares a name, environment, consumer path, retention, batch size/wait, retry policy, optional dead-letter queue, and optional concurrency cap. Publish batches contain at most 100 messages and are accepted atomically. When retries are exhausted, inspect and deliberately replay or purge dead letters:
Use @korve-dev/sdk to publish and verify deliveries. See the Runtime SDK and Queues API.