Is this project still alive?

[railsmechanic]

Because of the lack of simple and reliable message queues, this project is one of my favorites for dispatching messages with Go, but the last commit is from 1st august 2014...

Is this project still alive?

[wellle]

Actually we have completely rewritten it internally and might push it here at some point. There are currently some dependencies to other internal packages that need to be resolved first.

[glkz]

@wellle do you have an estimated/planned time to release the new version?

[wellle]

No not really, sorry.

[zhouseahe]

It would be better if there are commits recently.

[mmcdole]

@wellle this seems like a pretty cool project. Would love to see the rewrite.

[wellle]

Still on my list 👍

[pior]

👍

[wellle]

Hey guys, I finally found some time to extract our new implementation and cleaned it up a bit. You can find it here: https://github.com/adjust/rmq/tree/v1

The initial pull request is pending and might be merged next week: wellle/rmq#1

Please take a look and let me know what you think 😉

[xujinzheng]

good news 👍

[glkz]

@wellle great! thanks.

[taylon]

Hey @wellle which one do you recommend to use in production as of right now? rmq or redismq?

[wellle]

I just merged wellle/rmq#1.

@taylon: We run rmq in production since March and we never had redismq running in production ourselves. But I believe others do.

I think redismq has some performance optimizations that rmq doesn't have yet. But rmq should be more robust and have the better interface. It's also more feature rich.