Skip to main content

RabbitMQ Stream tutorial - "Hello World!"




This tutorial assumes RabbitMQ is installed, running on localhost and the stream plugin enabled. The standard stream port is 5552. In case you use a different host, port or credentials, connections settings would require adjusting.

Using docker

If you don't have RabbitMQ installed, you can run it in a Docker container:

docker run -it --rm --name rabbitmq -p 5552:5552 -p 15672:15672 -p 5672:5672  \
-e RABBITMQ_SERVER_ADDITIONAL_ERL_ARGS='-rabbitmq_stream advertised_host localhost' \

wait for the server to start and then enable the stream and stream management plugins:

docker exec rabbitmq rabbitmq-plugins enable rabbitmq_stream rabbitmq_stream_management 

Where to get help

If you're having trouble going through this tutorial you can contact us through the mailing list or discord community server.

RabbitMQ Streams was introduced in RabbitMQ 3.9. You can find more information here.

"Hello World"

(using the .NET/C# Stream Client)

In this part of the tutorial we'll write two programs in C#; a producer that sends a single message, and a consumer that receives messages and prints them out. We'll gloss over some of the detail in the .NET client API, concentrating on this very simple thing just to get started. It's the "Hello World" of RabbitMQ Streams.

The .NET stream client library

RabbitMQ speaks multiple protocols. This tutorial uses RabbitMQ stream protocol which is a dedicated protocol for RabbitMQ streams. There are a number of clients for RabbitMQ in many different languages, see the stream client libraries for each language. We'll use the .NET stream client provided by RabbitMQ.

The client supports .NET. This tutorial will use RabbitMQ .NET stream client 1.8.0 and .NET, so you make sure you have it installed and in your PATH.

RabbitMQ .NET stream client 1.8 and later versions are distributed via nuget.

This tutorial assumes you are using PowerShell on Windows. On MacOS and Linux nearly any shell will work.


First let's verify that you have the .NET toolchain in PATH:

dotnet --help

Running that command should produce a help message.

An executable version of this tutorial can be found in the RabbitMQ tutorials repository.

Now let's generate two projects, one for the publisher and one for the consumer:

dotnet new console --name Send
mv Send/Program.cs Send/Send.cs
dotnet new console --name Receive
mv Receive/Program.cs Receive/Receive.cs

This will create two new directories named Send and Receive.

Then we add the client dependency.

cd Send
dotnet add package RabbitMQ.Stream.Client
cd ../Receive
dotnet add package RabbitMQ.Stream.Client

Now we have the .NET project set up we can write some code.


We'll call our message producer (sender) Send.cs and our message consumer (receiver) Receive.cs. The producer will connect to RabbitMQ, send a single message, then exit.

In Send.cs, we need to use some namespaces:

using System.Text;
using RabbitMQ.Stream.Client;
using RabbitMQ.Stream.Client.Reliable;

then we can create a connection to the server:

var streamSystem = await StreamSystem.Create(new StreamSystemConfig());

The entry point of the stream .NET client is the StreamSystem. It is used for configuration of RabbitMQ stream publishers, stream consumers, and streams themselves.

It abstracts the socket connection, and takes care of protocol version negotiation and authentication and so on for us.

This tutorial assumes that stream publisher and consumer connect to a RabbitMQ node running locally, that is, on localhost. To connect to a node on a different machine, simply specify target hostname or IP address on the StreamSystemConfig.

Next let's create a producer.

The producer will also declare a stream it will publish messages to and then publish a message:

await streamSystem.CreateStream(new StreamSpec("hello-stream")
MaxLengthBytes = 5_000_000_000

var producer = await Producer.Create(new ProducerConfig(streamSystem, "hello-stream"));

await producer.Send(new Message(Encoding.UTF8.GetBytes($"Hello, World")));

The stream declaration operation is idempotent: the stream will only be created if it doesn't exist already.

A stream is an append-only log abstraction that allows for repeated consumption of messages until they expire. It is a good practice to always define the retention policy. In the example above, the stream is limited to be 5 GiB in size.

The message content is a byte array. Applications can encode the data they need to transfer using any appropriate format such as JSON, MessagePack, and so on.

When the code above finishes running, the producer connection and stream-system connection will be closed. That's it for our producer.

Each time the producer is run, it will send a single message to the server and the message will be appended to the stream.

The complete Send.cs file can be found on GitHub.

Sending doesn't work!

If this is your first time using RabbitMQ and you don't see the "Sent" message then you may be left scratching your head wondering what could be wrong. Maybe the broker was started without enough free disk space (by default it needs at least 50 MB free) and is therefore refusing to accept messages. Check the broker log file to see if there is a resource alarm logged and reduce the free disk space threshold if necessary. The Configuration guide will show you how to set disk_free_limit.

Another reason may be that the program exits before the message makes it to the broker. Sending is asynchronous in some client libraries: the function returns immediately but the message is enqueued in the IO layer before going over the wire. The sending program asks the user to press a key to finish the process: the message has plenty of time to reach the broker. The stream protocol provides a confirm mechanism to make sure the broker receives outbound messages, but this tutorial does not use this mechanism for simplicity's sake.


The other part of this tutorial, the consumer, will connect to a RabbitMQ node and wait for messages to be pushed to it. Unlike the producer, which in this tutorial publishes a single message and stops, the consumer will be running continuously, consume the messages RabbitMQ will push to it, and print the received payloads out.

Similarly to Send.cs, Receive.cs will need to use some namespaces:

using System.Text;
using RabbitMQ.Stream.Client;
using RabbitMQ.Stream.Client.Reliable;

When it comes to the initial setup, the consumer part is very similar the producer one; we use the default connection settings and declare the stream from which the consumer will consume.

Note that the stream name must match that used by the producer.

var streamSystem = await StreamSystem.Create(new StreamSystemConfig());

await streamSystem.CreateStream(new StreamSpec("hello-stream")
MaxLengthBytes = 5_000_000_000

Note that the consumer part also declares the stream. This is to allow either part to be started first, be it the producer or the consumer.

The Consumer class is used to instantiate a stream consumer and the ConsumerConfig record to configure it. We provide a MessageHandler callback to process delivered messages.

The OffsetSpec property defines the starting point of the consumer. In this case, the consumer starts from the very first message available in the stream.

var consumer = await Consumer.Create(new ConsumerConfig(streamSystem, "hello-stream")
OffsetSpec = new OffsetTypeFirst(),
MessageHandler = async (stream, _, _, message) =>
Console.WriteLine($"Stream: {stream} - " +
$"Received message: {Encoding.UTF8.GetString(message.Data.Contents)}");
await Task.CompletedTask;

The complete Receive.cs file can be found on GitHub.

Putting It All Together

In order to run both examples, open two terminal (shell) tabs.

Both parts of this tutorial can be run in any order, as they both declare the stream. Let's run the consumer first so that when the first publisher is started, the consumer will print it:

cd Receive
dotnet run

Then run the producer:

cd Send
dotnet run

The consumer will print the message it gets from the publisher via RabbitMQ. The consumer will keep running, waiting for new deliveries. Try re-running the publisher several times to observe that.

Streams are different from queues in that they are append-only logs of messages that can be consumed repeatedly. When multiple consumers consume from a stream, they will start from the first available message.