PPQPush Pull Queue

A small, self-hosted message queue broker — HTTP/JSON API, SQLite storage with one database per queue, at-least-once delivery, and three ways to consume: pull, long poll, or push.

Overview

Quick start

HTTP API

Client guides

At-least-once, by leases

Receive claims messages atomically and hands out a lease token per delivery. Stale workers cannot Ack a newer delivery, and expired leases are redelivered without a background job.

Push, pull or long poll

Workers poll, long-poll for up to 20 s, or register a callback URL and get notified when a queue has work — then fetch with the same Receive call.

Standard and FIFO queues

FIFO queues keep order within each message group, with one message per group in flight. Retries, dead letters, redrive, deduplication and delays are built in.

SQLite, one file per queue

No external database. Each queue has its own file, writer and lock; group commit batches concurrent Sends into one transaction.

Crash-tested

Tests kill the broker with SIGKILL mid-Send, mid-claim, mid-consume and mid-cleanup, then verify nothing acknowledged was lost or duplicated.

Secure by default

API keys with per-queue permissions, TLS enforced on public addresses, rate and concurrency limits, SSRF-protected push, owner-only data files.