alternative package

[iamfarhad]

Since the original package is no longer maintained and hasn’t received updates in a long time, I decided to create my own Laravel package that supports Laravel versions 10 and 11 for working with RabbitMQ.

My package is actively maintained and regularly updated to ensure compatibility and stability with the latest Laravel releases.

Feel free to check it out and use it in your projects:

🔗 LaravelRabbitMQ on GitHub

[oprudkyi]

Hi,
for some reason your package doesn't contain many commits from original one

[boserup]

Interesting. What are the overlap between the two packages? What is missing and what is new?

[iamfarhad]

Thanks for your feedback!

My package currently doesn’t support Horizon. The focus is on performance and keeping the package consistently up to date.

Please support me by using the package and giving it a star.

[nathangoss]

If the focus is on keeping the package up to date, will it be supporting Laravel 12 anytime soon?
Cheers

[iamfarhad]

If the focus is on keeping the package up to date, will it be supporting Laravel 12 anytime soon? Cheers

Laravel 12 is currently supported as well.

[fontebasso]

Hi @iamfarhad, great to see alternative solutions being shared. It really shows how important this package still is to the community.

Thanks for taking the time to maintain compatibility with newer Laravel versions. I just wanted to point out that there have been some recent contributions to this repository, and with a bit of collective effort, we can definitely keep things moving at a better pace.

It might be more productive for us to collaborate directly through PRs here, so we can avoid fragmentation and keep the main package strong and reliable for everyone.

This issue might be ready to close now that community activity has picked up again. Appreciate you starting the conversation and helping drive things forward!

[razvanphp]

I second @fontebasso, it's such a shame that this is not a native driver and effort is spread across many forks that will eventually get abandoned.

We better rewrite this following the strict Laravel style guide and convince Taylor to merge it in the original framework 🙂