Skip to content
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

Any plans to support Sidekiq backend? #47

Open
harlow opened this issue Nov 27, 2016 · 4 comments
Open

Any plans to support Sidekiq backend? #47

harlow opened this issue Nov 27, 2016 · 4 comments

Comments

@harlow
Copy link

harlow commented Nov 27, 2016

Not sure if this is on the radar, but has any thought gone into supporting Sidekiq too?

@rjrobinson
Copy link

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

@benmanns
Copy link
Owner

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?

@harlow
Copy link
Author

harlow commented Nov 27, 2016

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.

@rjrobinson
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants