Session
Symfony Messenger in production: what actually breaks
Long running workers and memory growth, closed entity managers, messages handled twice, dispatching inside a transaction that rolls back, deploys breaking deserialization, retries and the failure transport, scaling, monitoring: the traps of running Symfony Messenger in production, drawn from public write-ups, post-mortems and upstream issues, each with symptom, cause and fix.
Mathieu Santostefano
Tech Expert / Symfony Core Team member
Niort, France
Links
Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.
Jump to top