Mastering message Queues
summary
Advocates a hexagonal app core that communicates only via messages on a bus, implemented with Symfony Messenger and pluggable transports like RabbitMQ AMQP transport. Shows three buses (command/query/event), middleware for validation and transaction rollback, and an envelope for per-message retry/validation settings. Demonstrates practical patterns: generate UUID in the controller so async create returns a URL, run workers with messenger:consume and supervisor, and use a failed queue retry sweep instead of immediate infinite retry.
AI-written summary · about
chapters (14)
- 0:00Intro
- 0:22The data structure
- 1:56Tobias Nyholm
- 2:08Open source
- 7:33Matthias Noback
- 10:15Hexagonal architecture
- 12:00Work queue
- 13:01Routing
- 13:41Topics
- 16:47Transports
- 23:27Multiple busses
- 27:21Send events from handler
- 28:39Requeue
- 34:29Envelope
related talks
02h 05mSymfony Messenger
41mSymfony Messenger: Queues, Workers and Much More!
44mSymfony Messenger: Messages, Queues, Workers and more
44mAn Introduction to Symfony Messenger
43mAsync with Messenger, AMQP and Mercure
59mA CQRS Approach with Api Platform and Symfony Messenger
46mReal-world Examples of Message Queue Usage: Insights from RabbitMQ
27mRuby Messaging Patterns