Skip to content

RabbitMQ Consumer Test Console

A tool for hitting a message consumer with traffic and watching retries, dead letters and back-pressure in real time.

Status
Shipped
Period
Aug 2026 – Sep 2026
Role
Solo
Stack
  • RabbitMQ
  • Java
  • Spring
  • Observability
On this page

The problem

Consumers behave well in unit tests and badly under load. I wanted to see retries, dead-lettering and back-pressure happen, rather than infer them from logs afterwards.

What I built

A small console that publishes configurable bursts of messages, injects failures at a chosen rate, and charts queue depth, redeliveries and dead letters as they happen.

What broke

My first retry policy retried immediately. Under a 20% failure rate it turned one slow dependency into a self-inflicted storm.

Next

Add a Kafka adapter so the same scenarios can be compared across brokers.

More builds

Other things I've built

  • In progress2026

    My First AI Agent

    An agent that plans and calls tools to finish a job — plus an honest account of where it lost the plot.

    Outcome Handles the lookup work reliably; a person still checks the answer.

    • AI
    • Python
    • LLM
  • Shipped2026

    Event-Driven Billing System

    Invoices and payments modelled as events, designed so a retry never charges anyone twice.

    • Kafka
    • Spring
    • PostgreSQL

Next

Building something similar?

I am happy to talk about the boring parts — design, failure modes, and the places I would not trust the first version.

Get in touch