You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Where Redis Streams allow Symfony Messenger to divide work across multiple consumers, Redis Pub/Sub would allow Symfony Messenger to spread one message to all consumers. See https://redis.io/docs/manual/pubsub/
Did you consider implementing pub/sub on the adapter as well?
Our use-case:
A cronjob triggers the generation of a huge xml file.
A container does the processing for that on the background in another container.
Once the background processing is finished, that background container needs to make the frontend facing containers (4 of them) aware that they should download the xml file to their local container.
Having pub/sub in Symfony Messenger would allow us to simply add an extra transport that is configured as pub/sub to make the last step of the use-case possible.
The text was updated successfully, but these errors were encountered:
Where Redis Streams allow Symfony Messenger to divide work across multiple consumers, Redis Pub/Sub would allow Symfony Messenger to spread one message to all consumers. See https://redis.io/docs/manual/pubsub/
Did you consider implementing pub/sub on the adapter as well?
Our use-case:
Having pub/sub in Symfony Messenger would allow us to simply add an extra transport that is configured as pub/sub to make the last step of the use-case possible.
The text was updated successfully, but these errors were encountered: