Messenger is great. But, we've only carried it 90% of the way. It's missing key features and key things to really make it as usable as it deserves to be. Similar to #30502 , I'd like to ask for help & ideas from the community to really make it shine.
(Note: in some of these cases, we just need more review & testing to help push PR's forward).
pending doc PRs pending doc issues [Messenger] Adding failure transport support #30970 [Messenger] RoutableMessageBus route to default bus #31288 [Messenger] Add a redis stream transport #30917 [Messenger] Allows to register handlers on a specific transport #30958 [Messenger] Remove base64_encode & use addslashes #30957 [Messenger][RFC] Generic TransportConfig stamp #30558 [Messenger] AMQP configuration and MessageBus::dispatch enhancements #29950 [Messenger] Add possibility to define routing key when sending message throught amqp #28772 [Messenger] Add Null Transport #29040 [Messenger] Add a "in-memory://" transport #29097 [Messenger] Ensure message is handled only once per handler #30020 [messenger] Adds a stamp to provide a routing key on message publishing #30008 [Messenger] Adding MessageCountAwareInterface to get transport message count #30757 The default message bus name should start with messenger. #30670 [Messenger][DX] Allow stamps to be passed directly to MessageBusInterface::dispatch() #30707 Changing to MessageDecodingFailedException so that invalid messages are rejected #30756 [Messenger] Adding the "sync" transport to call handlers synchronously #30759 Avoid dispatching SendMessageToTransportsEvent on redeliver #30676 [Messenger] ReceiverInterface::handle() to get() & Worker with prioritized transports #30708 Making the serializer configurable by transport #30628 [Messenger] Add a Doctrine transport #29007 some basic adapters in core)[Messenger] New messenger:stop-workers Command #30754 [Messenger] add welcome notice when running the command #29303 messenger:consume has no output[Messenger] Worker events + global retry functionality #30557 [RFC][Messenger] General message retry mechanism #27215 [Messenger][AmqpExt] Add a retry mechanism for AMQP messages #27008 [Messenger] Worker events + global retry functionality #30557 [Messenger] Add "--force-consumption" option to force the consumption of messages #29132 messenger:consume not fail when a worker fails[Messenger] Worker events + global retry functionality #30557 [Messenger] Changing message handling log levels to higher levels #30764 Dispatching two events when a message is sent & handled #30650 [Messenger] messenger:consume - bus should be determined automatically #30631 [Messenger][RFC] Allow handler to choose the transport #30634 [Messenger] Add a command to setup transports #29476 [Messenger] Support for handling messages after current bus is finished #28849 Add optional parameter prefetching for AMQP connection #30671
What else?
Messenger is great. But, we've only carried it 90% of the way. It's missing key features and key things to really make it as usable as it deserves to be. Similar to #30502, I'd like to ask for help & ideas from the community to really make it shine.
(Note: in some of these cases, we just need more review & testing to help push PR's forward).
messenger.#30670 make sure bus service ids are consistentmessenger:consumehas no output[RFC][Messenger] General message retry mechanism #27215[Messenger][AmqpExt] Add a retry mechanism for AMQP messages #27008) Retry mechanism[Messenger] Add "--force-consumption" option to force the consumption of messages #29132) Makingmessenger:consumenot fail when a worker fails[Messenger][RFC] Allow handler to choose the transport #30634 Possibly allow each handler of a message to be sent to a different transport (e.g. 1 handler async, 1 sync) and when received, only the 1 handler is executed.prefetchingfor AMQP connection #30671 amqp prefetchWhat else?