Get background jobs processor in place

[pete2786]

We need to background things like Slack notifications, emails and possibly other long running operations eventually as we grow the app engagement (badges, recommendations).

We could also consider using active job to KISS: http://edgeguides.rubyonrails.org/active_job_basics.html

We could start with Delayed Job and eventually migrate to another, which provides nice flexibility. Here is the current list: http://api.rubyonrails.org/classes/ActiveJob/QueueAdapters.html

[pete2786]

H/T: to @chadfennell getting Rails upgraded to 4.2 making this an options 👍

[chadfennell]

Np, happy to do so :).

I am a big fan of Sidekiq - it's actually quite simple to install and manage. But yeah, makes sense to move these into the background for sure.

FWIW, I would suggest using sidekiq over Delayed Job since Sidekiq is so simple to get going with and because it sets us up for a better long-term path (see https://github.com/mperham/sidekiq/wiki/FAQ).

I haven't used SK with Active Job yet though, which seems like a good path. I am happy to help with this task.

[pete2786]

I use and love sidekiq. Originally I wrote this story as add sidekiq, but I did not want to have to add another dev dependency (redis).

However, you want to tackle it and want to use sidekiq, go for it.

[chadfennell]

sure, good instinct in general, yes.