How to stream Postgres to RabbitMQ

This guide shows you how to set up Postgres change data capture (CDC) and stream changes to RabbitMQ using Sequin.

With Postgres data streaming to RabbitMQ, you can trigger workflows, keep services in sync, build audit logs, maintain caches, and more.

By the end of this how-to, you’ll have database changes flowing to a RabbitMQ exchange.

​

Prerequisites

If you’re self-hosting Sequin, you’ll need:

1. Sequin installed
2. A database connected
3. A RabbitMQ server ready to go

If you’re using Sequin Cloud, you’ll need:

1. A Sequin Cloud account
2. A database connected
3. A RabbitMQ server ready to go

​

Basic setup

​

Prepare RabbitMQ

You’ll need a RabbitMQ server and exchange ready for Sequin to stream changes to. You can use either a local server for development or a cloud-hosted RabbitMQ service in production.

​

Local development with Docker

For local development, you can quickly spin up RabbitMQ using Docker:

docker run -d --name rabbitmq \
  -p 5672:5672 \
  -p 15672:15672 \
  rabbitmq:3-management

This starts RabbitMQ with the management plugin enabled at http://localhost:15672 (login with guest/guest).

​

Configure RabbitMQ

Before creating your sink, set up RabbitMQ to receive messages:

1. Create an exchange:
   • Name: Choose a name for your exchange (e.g., “sequin”)
   • Type: topic
2. Create a queue:
   • Name: Choose a name for your queue (e.g., “my-table-changes”)
3. Create a binding:
   • From exchange: The exchange you created
   • To queue: The queue you created
   • Routing key: sequin.changes.<database>.<schema>.<table>.* This routing key pattern will match all changes to your table. The format is: sequin.changes.<database>.<schema>.<table>.<action>

​

Create RabbitMQ sink

Navigate to the “Sinks” tab, click “Create Sink”, and select “RabbitMQ Sink”.

​

Configure the source

​

Configure RabbitMQ

​

Verify & debug

To verify that your RabbitMQ sink is working:

1. Make some changes in your source table
2. Verify that the count of messages for your sink increases in the Sequin web console
3. Using the RabbitMQ management UI or CLI, check your queue:

   rabbitmqadmin get queue=your-queue count=5
   

   You should see the messages from Sequin appear in the queue.

If messages don’t seem to be flowing:

1. Click the “Messages” tab to view the state of messages for your sink
2. Click any failed message
3. Check the delivery logs for error details, including any RabbitMQ connection errors

​

Next steps

• Setup a consumer

  Now that your Postgres data is flowing into RabbitMQ, you can setup a consumer to read from the queue and process the data.

  Refer to the RabbitMQ sink reference for the shape of messages that Sequin will publish.

• Deploy your implementation

  When you’re ready to deploy your implementation, see “How to deploy to production”.

• Advanced configuration

  For more about how RabbitMQ sinks work, see the RabbitMQ sink reference.