While simplifying the code base is a worthy goal, I believe RabbitMQ should remain available in the core.
Why RabbitMQ matters:
* Scalability: Handles spikes in email sends or events by queuing tasks and processing them in parallel.
* Reliability: Provides durability, retries, and dead-letter queues so no messages are lost during failures.
* Enterprise use cases: Many organizations rely on RabbitMQ for high-volume marketing operations.
* Flexibility: Features like routing, priority, and delayed retries enable more complex workflows.
* Compatibility: Existing Mautic users already run RabbitMQ setups; removing it forces disruptive installs or migrations.
Suggestion:
Keep RabbitMQ in the core or at the very least as an optional queue transport, just like Redis or database queues. This way smaller users stay on simple options, while larger/enterprise users retain the advanced features they depend on.
Removing RabbitMQ risks limiting Mautic’s scalability and enterprise adoption. Keeping it modular ensures the best of both worlds: lean core and enterprise readiness.
The AMQP transport requires the AMQP PHP extension and a running AMQP service like RabbitMQ and a Composer dependency installed via composer require symfony/amqp-messenger.
RabbitMQ has been a core part of Mautic for years and is relied on by many users, especially at scale. Removing it unilaterally in Mautic 7 Alpha creates unnecessary disruption and undermines upgrade confidence. Keeping it in the core maintains continuity, preserves user choice, and allows the community to decide on any future deprecation through an open and structured process.
Your original justification for removing RabbitMQ was to make “upgrades easier” and not to improve or enhance Mautic etc. In fact its loss to the Mautic’s core is detrimental to the whole project and especially those who want to run at scale. Or are you developing for users with less than 100 contacts on an instance.
I again request that RabbitMQ be left in the core of M7 and open up a community discussion about removing it in M8 and allow the community time to respond and comment rather than unilaterally removing it without notice in the M7 Alpha.