New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Information about the MrQ status #70
Comments
Hey Frank :) Yes, we are just getting ready for our first officially supported release (0.9.0)! MRQ has been used in production at Pricing Assistant for 1 year, processed more than 1 billion jobs, so we're pretty confident by now! Several other 3rd party projects have begun using it, some in "serious" production too. Let us know if you need help! The "get started" should make some sense: Cheers, |
Ok we'll play with it and will come back to you when we decide to use it or not. Thank you for the information. |
Ok MrQ looks very good. But I have two questions:
|
One more question:
|
Sorry for the lag - Friday was dotSwift :/
Thanks! |
No problem for the delay and thank you for you answer. Finally, we developed our own solution. We don't have much jobs to handle currently and we were in a rush. So, it will be temporarly fine. Our use case is simple : we spawn containers on which we apply a sery of actions. That actions should be runned sequentially and there is something like 16 actions. We want to track every result to be able to restart failed jobs. Some jobs must be runned 24h later the previous job. At first, we tried your solution to run the job the previous one finished. But, because of the numerous jobs, it made things a little bit messy. And we prefer to describe the whole workflow in one place. NB: To be honest, we do it sequentially to keep things simple. But, a workflow engine would probably be better NB: Congrats for the DotSwift, I saw the pictures, it looked great! I want the Dot stickers too ;) |
Thanks! |
And thank you for the upcoming snippets, it will be useful when we will try to integrate MrQ again. |
Hello PricingAssistant,
We are implementing a task-based processing for our infrastructure management API requests. We are looking for Python queue frameworks. At first, we were interested in using Celery+Redis for it. Then we remembered that RQ was a lighter alternative. After digging into the subject, we discovered your project.
From what says your README, it looks like the proper solution for us: simple as RQ, stores results in a MongoDB instance, comes with a beautiful dashboard.
So my question is can we try to use MrQ for our infrastructure API? Is it easy to start with?
The text was updated successfully, but these errors were encountered: