【Rails8】Solid Queueでのエラー解消までのメモ
https://qiita.com/koxrtx/items/f379913a6f1110b5366a?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items
【Rails8】Solid Queueでのエラー解消までのメモ
https://qiita.com/koxrtx/items/f379913a6f1110b5366a?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items
SolidQueue, the default ActiveJob's adapter in Rails, is very cool. But there is a catch - it needs 1Gb RAM to make all things out of the box working fine. That means it's not good for Heroku default Dynos. Surprise - https://github.com/rails/solid_queue/issues/330#issuecomment-3387827039
Episode #520 - Worker Limits
#ruby #rubyonrails #programming #code #background #jobs #solidqueue
In this episode, we look at situations when an external API does not have a normal rate limit, but instead has concurrency limits. This can also apply to situations where you have limited resources on the API that you're calling. This can also work well in other situations where the background job is accessing limited resources.
A Deep Dive into Solid Queue for Ruby on Rails
https://blog.appsignal.com/2025/06/18/a-deep-dive-into-solid-queue-for-ruby-on-rails.html
#HackerNews #SolidQueue #RubyOnRails #DeepDive #AppSignal #TechBlog
An Introduction to Solid Queue for Ruby on Rails
https://blog.appsignal.com/2025/05/07/an-introduction-to-solid-queue-for-ruby-on-rails.html
#HackerNews #SolidQueue #RubyOnRails #Introduction #AppSignal #TechBlog
Episode #498 - Conditional Queue
#ruby #rubyonrails #solidqueue #backgroundjobs #programming #code
In this episode we look at processing background jobs in a way that can conditionally send the work to be processed to different queues. This can be very powerful in situations where you need to process the job in different ways or send requests to different APIs.
It's always great to see @rosa and she talked about her #SolidQueue implementation at #rubycommunityconference in #krakow.
She also gave a shout-out to @bensheldon's #goodjob and mentioned how @getajobmike's @sidekiq is blazingly fast.
#ruby #rails #queue #rubyonrails #activerecord #poland #37signals #backgroundprocessing #backgroundprocesses #sidekiq
I'm adding background jobs to my new app (Rails7.2 + SolidQueue), and not sure how things should be designed.
I need to run daily job to generate notifications on user-created task due/reminder date.
Should I:
1) create one job that iterates all relevant tasks and generates notifications? (might get slow with more users)
2) have one job that iterates tasks, and creates separate job for every relevant task?
3) something else?