RelayMQ

Problem

Running background jobs usually means standing up a heavyweight messaging stack, then assembling a separate monitoring stack just to find out why a message failed or got delivered twice.

What I did

Building RelayMQ in Rust: a lightweight, local-first broker that makes it easy to see what is happening inside your queues, and why. Four pillars:

1. 01Dead-simple setupInstall, start, create a queue and publish a message in minutes. Sensible defaults, minimal configuration.
2. 02Lightweight messagingA single-node broker for background jobs, with clear delivery and acknowledgement semantics.
3. 03First-class observabilityInspect queues, messages, consumers, delivery attempts, failures and redeliveries without assembling a separate monitoring stack.
4. 04An immersive UIA live topology and message-lifecycle view, with interactive failure simulations that make the system's behaviour tangible.

What happened

In active development.