# symfony/messenger

Helps applications send and receive messages to/from other applications or via message queues

Repository: https://github.com/symfony/messenger
Canonical: https://ross.abutalabs.com/products/symfony-messenger
Homepage: https://symfony.com/messenger
Language: PHP
License: MIT
License Family: permissive
Topics: php, component, symfony-component, symfony
Last push: 2026-09-02T15:09:14+00:00

## Health v2 (maintenance only)
Score: 96/100 (v2, computed 2026-09-03T02:39:23.370411+00:00)
- activity 100, release rhythm 88, longevity 100
- inputs: {"age_days": 3085, "days_push": 0, "days_rel": 3, "gap_med": 0.0, "n_releases_24m": 79}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 1110, forks 95 (observed 2026-09-03T02:15:18.333651+00:00)

## What it is
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
- artifact type: library
- maturity: stable
- function: message-queue, middleware, serialization
- domain: backend, web-development, microservices
- platform: php
- tags: 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

## Member repositories
- symfony/messenger (main) score 96

## Provenance
- Observed fields: from GitHub, fetched 2026-09-03T02:15:18.333651+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T06:43:32.345703+00:00, confidence not recorded.
  - readme: https://github.com/symfony/messenger (fetched 2026-09-03T02:15:18.333651+00:00, sha 3b23d5fc3e69)
  - homepage: https://symfony.com/messenger (fetched 2026-08-29T12:47:00.738494+00:00, sha cb115bb84a77)
  - site_page: https://symfony.com/doc (fetched 2026-08-29T12:47:00.741079+00:00, sha 44889134f4fb)
  - site_page: https://symfony.com/doc/current/components/messenger.html (fetched 2026-08-29T12:47:00.743465+00:00, sha 6daed118f5ad)
  - site_page: https://symfony.com/releases (fetched 2026-08-29T12:47:00.749690+00:00, sha a53ecdd1cdf8)
  - site_page: https://symfony.com/blog/category/releases (fetched 2026-08-29T12:47:00.752003+00:00, sha f9d5d2a27917)
- Data as of 2026-08-30T08:39:29.467469+00:00.