symfony/messenger
Helps applications send and receive messages to/from other applications or via message queues observed · 2026-09-03
Health v2 · maintenance only
96/100
- Activity 100
- Release rhythm 88
- Longevity 100
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.
- gap_med: 0.0
- age_days: 3085
- days_rel: 3
- days_push: 0
- n_releases_24m: 79
Adoption not part of the score
1110 stars · 95 forks observed · 2026-09-03
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded
Symfony Messenger is a PHP component that helps applications send and receive messages to other applications or via message queues. It provides message buses with middleware, routing of messages to transports such as AMQP, Redis, Amazon SQS, Beanstalkd, or Doctrine, and worker commands for asynchronous consumption with retries, failure transports, and message serialization.
Use cases
- send messages asynchronously between php applications
- process background jobs in a symfony app
- queue tasks with rabbitmq, redis, or amazon sqs in php
- implement a command bus or cqrs pattern in symfony
- retry and store failed messages from a queue
- decouple microservices via message queues
- run a message consumer worker in php
When to choose
- You are building a PHP or Symfony application that needs queued or asynchronous message handling
- You want a transport-agnostic message bus with official support for AMQP, Redis, SQS, Beanstalkd, and Doctrine transports
- You need command/query bus separation, middleware, prioritized transports, or built-in retry and failure handling
- You want a battle-tested solution already used at scale by major PHP projects like Symfony itself, TYPO3, PrestaShop, Sylius, and Shopware
When to avoid
- You are not working in PHP or the Symfony ecosystem
- You need an actual message broker - Messenger connects to brokers like RabbitMQ but is not a broker itself
- You need full workflow orchestration or scheduled job management rather than message dispatch and consumption
- You want a language-agnostic or standalone queueing service rather than an in-process component
Facets
library · maturity stable
message-queue middleware serialization backend web-development microservices php symfony message-bus command-bus cqrs async-processing queue-worker amqp redis-transport amazon-sqs doctrine-transport retry-failure-handling event-driven-architecture transport-abstraction php-component messaging
6 sources
- readme: https://github.com/symfony/messenger · fetched 2026-09-03 · 3b23d5fc3e69
- homepage: https://symfony.com/messenger · fetched 2026-08-29 · cb115bb84a77
- site_page: https://symfony.com/doc · fetched 2026-08-29 · 44889134f4fb
- site_page: https://symfony.com/doc/current/components/messenger.html · fetched 2026-08-29 · 6daed118f5ad
- site_page: https://symfony.com/releases · fetched 2026-08-29 · a53ecdd1cdf8
- site_page: https://symfony.com/blog/category/releases · fetched 2026-08-29 · f9d5d2a27917
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| symfony/messenger | main | 96 |
For agents
markdown · JSON · MCP: product_card(name="symfony/messenger")
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem