<FromGitter>
<straight-shoota> Oh, that hasn't been on my radar
<FromGitter>
<jwoertink> I was using mosquito which works well under small load, but seems to have some issues under high load. I tried sidekiq, and it just seemed to be a mess. I spent a while trying to get it configured, and just couldn't get it to run
<FromGitter>
<jwoertink> We're using this Tasker on another project for cron stuff, so gonna try it for the background runner stuff now.
<FromGitter>
<jwoertink> So far integrated super easy, and works well in development.
<FromGitter>
<straight-shoota> Honestly, I think each of the currently available shards has conceptual design issues. And most of them don't seem under active development.
<FromGitter>
<straight-shoota> tasker works only in-memory, right?
<FromGitter>
<jwoertink> Yeah. Just in memory
<FromGitter>
<jwoertink> which is a downside. Not sure how this will work if we deploy while stuff is running... but... here goes nothing! 😂
<FromGitter>
<straight-shoota> That's definitely a constraint. But might be okay for now
<FromGitter>
<jwoertink> That's what I'm thinking. It gets the job done for now
<FromGitter>
<Blacksmoke16> Could always just use rabbit, but build a layer on top of it
<FromGitter>
<jwoertink> rabbitmq ?
<FromGitter>
<straight-shoota> There's definitely a need for a sophisticated background job worker in the ecosystem. I mean it doesn't need to have fancy features, a really basic solution would be fine. As long as its well designed, growing more features is not an issue.
<FromGitter>
<jwoertink> Mosquito actually works really well and is super simple. I think it just needs a little love
<FromGitter>
<jwoertink> but it's a great start
<FromGitter>
<jwoertink> The issue I ran in to with that was if I ran just 1 worker at a time, it was fine. But queueing up 4 workers at the same time would give unexpected results of some would run and some wouldn't
<FromGitter>
<Blacksmoke16> I wanted to make some framework around rabbitmq, like for creating consumers, publishing to a queue etc
<FromGitter>
<Blacksmoke16> Then everything is based on a well used system versus doing everything from scratch
<FromGitter>
<straight-shoota> mosquito is quite nice for the most part. But the custom serialization it employs to stuff all job arguments into a redis hash is really weird-
sagax has quit [Remote host closed the connection]
<FromGitter>
<straight-shoota> @Blacksmoke16 My vision would be to have a generic framework similar to ActiveJob which can be used with pluggable backends. The integration into an application is usually pretty similar, whether you're running your job queue in memory, database, redis or rabbitmq etc. That way you can easily choose the backend that fits best for the specific use case, even use different ones for different