How to use Solid Queue in Ruby on Rails

► Check out gorails.com for Pro episodes and more!
► SaaS business template for Ruby on Rails with built-in features like Payments, Teams, and much more: jumpstartrails.com
► Ruby on Rails hosting with Hatchbox.io: hatchbox.io
► Learn how to add Stripe Payments (with SCA support!) with Ruby on Rails: courses.gorails.com/payments-...

[@CarlFyffe]

What's the best way to decrease the logging? That's a ton of noise that is distracting from watching for those pesky N+1 queries and other important messages while developing.

[@askegg]

It's great to have this as standard and simplify deployment for beginner apps. We can always migrate to another solution should we ever grow out of solid queue, but given 37 Signals seems to be moving to this in their production environment it's probably unlikely most of us will ever need to.

[@GorailsTV]

Yep! Also I think this is particularly helpful for their new ONCE products that will need easy deployments for people unfamiliar with Rails.

[@n00bma5ter69]

Damn you were quick with this one. Great vid!!

[@GorailsTV]

Trying to stay on the bleeding edge!

[@timbarkleymusic]

Thanks for the video! Since the job details are stored in the db, would we want to regularly clean up the tables to not waste space?

[@EstoyProgramando]

Nice video, thank you, I will start looking on how to do job uniqueness, callbacks, batches, monitoring and scheduling. There is no really an API I think one would have to query directly the database to do what I mentioned before.

[@shayani]

Thanks for the video! Do you know if solid queue supports or will support scheduled jobs, like a job that should run everyday at a specific time?

[@mauriciomdea]

Maybe this is a stupid question, but why so many tables? Why use different tables for blocked, claimed and failed executions and not just a flag? Hope you enlighten me! 😅

[@brianmichel]

Chris, awesome run down as always! Curious if you’ve tried litestack and what your thoughts are on SQLite as a production db with litestack to handle jobs and caching.

[@GorailsTV]

Haven't tried it yet but I've heard good things and it sounds wonderfully simple to maintain.

[@torvic99]

NICE.

[@melvinrram]

I'm curious on the performance of this vs Resque. I had done a test using just an empty job with ActiveJob and Resque job at one point. ActiveJob was a little less than 2x slow than basic Resque job. I'm curious about Resque job + Resque vs ActiveJob + SolidQueue performance for the same workload. I'll likely do this at some point but if someone has done it already, I'd love to see it.

[@TungNguyen-om6px]

It would be great if Solid_queue had a UI

[@okoni.alesre]

скоро будет.

[@GorailsTV]

It will! DHH announced Mission Control which will be a UI for ActiveJob coming soon.

[@americosavinon]

Chris do you see solid_queue potentially eating most of Sidekiq's lunch?

[@GorailsTV]

Too early to tell since this is brand new and Sidekiq is battle tested in many, many big companies and use cases. I think the simplicity of this will be a strong selling point and will probably become most people's default.