Skip to main content
Back to Dev generators

Dev

Mock RabbitMQ Message Generator

Used by developers, writers, and creators worldwide.

A mock RabbitMQ message generator produces fake message-queue payloads with routing metadata for testing and learning. Message queues move data between services asynchronously, and a message carries not just a payload but routing information — an exchange, a routing key, and properties like a message id and delivery mode. This tool emits a realistic message object with all of that. Click generate and copy it into a test or a tutorial. It is ideal for testing a consumer, building a mock queue, and learning message structure. The message reflects the real shape RabbitMQ uses, so it shows how the payload travels with its exchange, routing key, and properties. The payload and ids are random and reference nothing real, which makes them safe to use freely. Adapt the exchange, routing key, and payload to your own system when you wire up a real queue and consumer.

Loading usage…

Free forever — no account required

How to use

  1. Choose your options above
  2. Click Generate
  3. Copy your result

Detailed instructions

  1. Click Generate to produce a queue message.
  2. Copy the JSON into a test or mock queue.
  3. Use it to exercise a consumer.
  4. Adapt the routing and payload to your system.

Use Cases

  • •Testing a message consumer
  • •Building a mock queue
  • •Learning message-queue structure
  • •Seeding sample messages
  • •Demoing async messaging

Tips

  • →Messages carry routing metadata.
  • →The routing key directs delivery.
  • →delivery_mode 2 means persistent.
  • →Adapt the payload to your system.

FAQ

what is in a message-queue message

Beyond the payload, a message carries routing information — an exchange and routing key that determine where it goes — and properties like a message id, content type, and delivery mode. This sample includes all of those, mirroring a real message.

what is a routing key

A routing key is a label the message broker uses to decide which queues a message is delivered to, based on the exchange's rules. Patterns like order.created let consumers subscribe to exactly the events they care about.

are these messages real

No. The payload and ids are randomly generated and reference nothing real, so they are safe to use freely in tests and demos. They follow the structure of a real message, which is what matters for exercising a consumer.