zlacker

Very nice and ambitious project. Did you compare vs Dramatiq? It was created to overcome same shortcomings of Celery.

>>llIIll+(OP)
I was initially excited when Dramatiq was released, but I think the GNU license prohibits using it for commercial projects?

Also, I really wanted something simple and easy to maintain after working around so many bugs. Dramatiq isn't as complicated as Celery but it still has features I don't need.

>>welder+a
It’s LGPL, which is usually fine if you’re just using it as-is.

>>Waterl+k
Maybe I should have used Dramatiq instead of building my own, but it's already done. I'm surprised how well WakaQ is working in production actually. If any issues come up they should be faster to fix than making PRs to Dramatiq.

>>welder+U
There’s nothing inherently wrong with doing it yourself if you’re consciously aware of the costs and benefits. Promise us you’ll do a blog post in a year talking about it, though! :)

>>welder+a
Thanks for honest answer. I hope you enjoyed the development of this software. I will use it the next time I need a queue.

>>llIIll+(OP)
Dramatiq is easy to daemonize which I like a about a lot but the schedule feature is not there and that's big drawback. I had to use my custom open source scheduler to schedule a function. https://github.com/rajasimon/beatserver

>>rajasi+ah
Periodiq is a nice scheduler, which works well with Dramatiq

>>welder+U
You are running this in production? I had a look at the github repo and did not find any tests. How are you QAing the project?

>>bosie+Ed1
I built a local test app that does have some integration tests, and then I just went all in on production. That's why I was surprised it worked so well. I was ready to lose a few nights sleep debugging it in prod, but thankfully didn't have to.