Any plans to support Sidekiq backend? about goworker HOT 4 OPEN

I was visiting this idea as well. But kind of make it for active job.

from goworker.

I would be interested in fully supporting Sidekiq. I'm more familiar with the insides of Resque than Sidekiq, but I believe they are similar (at least standard enqueue/dequeue). Do you know what features would need to be implemented for compatibility?

from goworker.

Do you know what features would need to be implemented for compatibility?

@benmanns will take a look this week; @rjrobinson maybe ActiveJob is better interface to build against (assuming it works w/ sidekiq)?

We're heavy Ruby/Sidekiq users and beginning to port a few of them to Go. Would def be interested in helping out if it's something that would fit nicely into this project.

from goworker.

ActiveJob has sidekiq support ( thats what I use.) . Let me dig a little deeper.

tbh.... we could just build out our own go version of a background service, that takes in json from redis.

I was always confused why go-worker took in an interface of interfaces. Seems like a json payload, and then marshaling it to a struct was a easier choice

from goworker.