Closed as not planned
Description
Description
Where #30958 relates to introducing more extensive pub/sub capabilities on the AMQP exchanges, the Redis adapter currently does not support pub/sub yet.
When looking into the other issues that mention pub/sub, it seems AMQP or an external Google Pub/Sub adapter seems to be the only way to support this: https://github.com/symfony/symfony/issues?q=is%3Aissue+pub%2Fsub
In other words, when solely using Redis transports (e.g. due to an infra SLA not allowing RabbitMQ), there is no way to let a single consumer (e.g. one on supervisor) notify all other consumers about an event that happened.
What would it take to introduce Redis Pub/Sub on the Redis Messenger integration?
Example
- Let a K8S scheduled cronjob dispatch generation of a huge xml file, by putting one message per chunk on the Redis Messenger transport
- Let 10 background worker containers do the processing of these chunks (100k messages)
- Let the "finalization" event handler wait until all processing is done and double check everything (1 message)
- Let that same finalization handler notify a "frontend" transport to which all publicly facing containers have subscribed.
- The frontend containers should then all fetch the updated version of the huge xml file from the shared storage (a S3 bucket)
Currently, the Redis transport does not support step 5.