symfony / mongodb-messenger

8.2.x-dev 2026-10-12 12:26 UTC

Requires

• php: >=8.4.1
• ext-mongodb: ^1.21|^2.0
• mongodb/mongodb: ^1.21|^2.0
• symfony/messenger: ^8.2

MIT

• Alessandro Lai
• Symfony Community

Published on Packagist.org on 2026-10-12 12:27 UTC

README

Provides MongoDB integration for Symfony Messenger.

DSN example

MESSENGER_TRANSPORT_DSN=mongodb://user:[e-mail]:27017/db_name?collection_name=messenger_messages&queue_name=default

The transport reads its own settings (database, collection_name, queue_name, redeliver_timeout) from the query string and passes any other parameter to the MongoDB driver, so connection options keep working:

MESSENGER_TRANSPORT_DSN=mongodb+srv://mongodb.example.com/db_name?replicaSet=repl&connectTimeoutMS=3000

Listening to several queues

A transport sends to a single queue, named by the queue_name option, and by default reads only from that queue. Queues listened to together by one receiver must live in the same namespace in the same MongoDB cluster, since the queue name is a field of the message document. Declare one transport per queue, so the routing can target each:

framework:
    messenger:
        transports:
            foo: 'mongodb://host/db?queue_name=foo'
            bar: 'mongodb://host/db?queue_name=bar'
        routing:
            App\FooMessage: foo
            App\BarMessage: bar

Then consume them all with one worker:

messenger:consume foo --queues=foo --queues=bar

A receiver consumes every listed queue with its own settings: with messenger:consume foo --queues=bar, a message of bar that exhausted its retries goes to the failure transport configured on foo.

See Limit Consuming to Specific Queues in the Messenger documentation.

Resources

• Contributing
• Report issues and send Pull Requests in the main Symfony repository