Symfony Messenger separates message dispatch from message handling. It can run handlers synchronously or send messages to a transport for asynchronous processing.
Define messages and handlers
Use small message objects that describe an intention or fact. Handlers perform the work and should depend on explicit services. Keep serialization compatibility in mind when messages may remain in a queue during deployments.
Configure transports and routing
Choose a transport appropriate to the deployment environment and route only the message classes that should be asynchronous. Local synchronous handling can simplify development, but staging should exercise the actual transport.
Handle failures
Configure retry strategies and a failure transport. Make handlers idempotent because messages can be delivered again. Track message age, retry counts and failure volume, and document a safe replay procedure.
Coordinate database writes
When a database transaction and message publication must agree, consider a transactional outbox rather than assuming two independent systems commit atomically.
Further reading
- Symfony Messenger: https://symfony.com/doc/current/messenger.html