The Solid Queue database-based backend for ActiveJob currently requires `fork` to work, solely because that's the only way to make sure it runs in parallel on CRuby. I want it to work on JRuby, which doesn't support fork, but can run threads in parallel very easily. Help?
buff.ly/18ZW69U
buff.ly/18ZW69U
Non-forking implementation · Issue #679 · rails/solid_queue
Hello! I would like to offer my help making modifications to Solid Queue to support executing in-process using threads rather than out-of-process as a fork. There's many issues with using fork: Imp...
github.com
November 4, 2025 at 9:47 PM
The Solid Queue database-based backend for ActiveJob currently requires `fork` to work, solely because that's the only way to make sure it runs in parallel on CRuby. I want it to work on JRuby, which doesn't support fork, but can run threads in parallel very easily. Help?
buff.ly/18ZW69U
buff.ly/18ZW69U
Upgrading to Rails 8.1 broke our serializers so I ended up rewriting my custom initializer to:
Rails.application.config.after_initialize do
ActiveJob::Serializers.add_serializers(
MySerializers
)
end
For some reason custom_serializers don't work here
Rails.application.config.after_initialize do
ActiveJob::Serializers.add_serializers(
MySerializers
)
end
For some reason custom_serializers don't work here
October 27, 2025 at 11:37 AM
Upgrading to Rails 8.1 broke our serializers so I ended up rewriting my custom initializer to:
Rails.application.config.after_initialize do
ActiveJob::Serializers.add_serializers(
MySerializers
)
end
For some reason custom_serializers don't work here
Rails.application.config.after_initialize do
ActiveJob::Serializers.add_serializers(
MySerializers
)
end
For some reason custom_serializers don't work here
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 - github.com/rails/solid_...
#rails #solidqueue #activejob #heroku
#rails #solidqueue #activejob #heroku
Need advice on Solid Queue's memory usage · Issue #330 · rails/solid_queue
Ruby: 3.3.4 Rails: 7.2.1 Solid Queue: 0.7.0, 0.8.2 I run a Rails App on AWS EC2 instance with 1G of memory. I notice the solid queue process takes up 15-20% of the instance's memory, which becomes ...
github.com
October 10, 2025 at 12:13 AM
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 - github.com/rails/solid_...
#rails #solidqueue #activejob #heroku
#rails #solidqueue #activejob #heroku
Not sure, need ActiveJob for that, so minimal API Rails would be OK for it.
Instead of Sinatra, I'd love to checkout @hanamirb.org :D
Instead of Sinatra, I'd love to checkout @hanamirb.org :D
September 30, 2025 at 10:02 PM
Not sure, need ActiveJob for that, so minimal API Rails would be OK for it.
Instead of Sinatra, I'd love to checkout @hanamirb.org :D
Instead of Sinatra, I'd love to checkout @hanamirb.org :D
Gotta give mad props to @seuros for shaking up the Rails error tracking game.
He’s building Lapsoss - a vendor-agnostic library for error tracking. Think ActiveJob, but for errors.
Switching from Sentry to Honeybadger? With Lapsoss, just change the adapter, the API stays the same.
He’s building Lapsoss - a vendor-agnostic library for error tracking. Think ActiveJob, but for errors.
Switching from Sentry to Honeybadger? With Lapsoss, just change the adapter, the API stays the same.
September 13, 2025 at 2:24 PM
Gotta give mad props to @seuros for shaking up the Rails error tracking game.
He’s building Lapsoss - a vendor-agnostic library for error tracking. Think ActiveJob, but for errors.
Switching from Sentry to Honeybadger? With Lapsoss, just change the adapter, the API stays the same.
He’s building Lapsoss - a vendor-agnostic library for error tracking. Think ActiveJob, but for errors.
Switching from Sentry to Honeybadger? With Lapsoss, just change the adapter, the API stays the same.
It's interesting that the new ActiveJob continuations seem limited in scope to "interrupting and resuming jobs" (ex. when job workers are rebooted on deploy), rather than generally resuming on failure. The latter would open the door for dealing with failure compensation (ie graceful rollback)
September 5, 2025 at 11:58 AM
It's interesting that the new ActiveJob continuations seem limited in scope to "interrupting and resuming jobs" (ex. when job workers are rebooted on deploy), rather than generally resuming on failure. The latter would open the door for dealing with failure compensation (ie graceful rollback)
More playing with event-sourced durable execution and Ruby: here the workflow defines custom context data that durable methods can use to keep track of progress (indices, cursors, etc). Similar to the step increments in the new "Continuations" in ActiveJob.
September 4, 2025 at 10:33 PM
More playing with event-sourced durable execution and Ruby: here the workflow defines custom context data that durable methods can use to keep track of progress (indices, cursors, etc). Similar to the step increments in the new "Continuations" in ActiveJob.
Good talk on durable execution and Ruby (using Temporal). Similar with Acidic Job and ActiveJob continuations, this pattern will only become more widespread. www.youtube.com/watch?v=IMAA...
SF Ruby Meetup, August 26 2025, Github HQ
YouTube video by Evil Martians
www.youtube.com
August 28, 2025 at 12:37 PM
Good talk on durable execution and Ruby (using Temporal). Similar with Acidic Job and ActiveJob continuations, this pattern will only become more widespread. www.youtube.com/watch?v=IMAA...
Which means you don't _have to_ use the built-in abstractions. Ex. you could build an ActiveJob-compatible API on top of this, and get traceable jobs for free ("job1 produced job2 which produced job3"). With execution history (ie "durable execution") to boot.
August 7, 2025 at 9:57 AM
Which means you don't _have to_ use the built-in abstractions. Ex. you could build an ActiveJob-compatible API on top of this, and get traceable jobs for free ("job1 produced job2 which produced job3"). With execution history (ie "durable execution") to boot.
https://anatofuz.hatenablog.com/entry/2025/07/25/190229
RubyでFCMのHTTPv1 APIをHTTP/2で扱うgem、ffccmmxがリリースされました。
HTTP/2対応により、複数人への通知が大幅に高速化されます。
多重送信機能やリトライ機能も備え、ActiveJobとの連携も容易です。
RubyでFCMのHTTPv1 APIをHTTP/2で扱うgem、ffccmmxがリリースされました。
HTTP/2対応により、複数人への通知が大幅に高速化されます。
多重送信機能やリトライ機能も備え、ActiveJobとの連携も容易です。
RubyでFCMのHTTPv1 APIをHTTP/2を使ってやりとりするffccmmxをリリースした - Acme::AnaTofuZ->new;
ということでgem作者になりました。どうぞお使いください。 rubygems.org RubyでFCMのAPIクライアントとしてはfcmpushやfcmが有名です。これらのgemは非常に使い勝手がいいのですが、使用するHTTPのプロトコルがライブラリの都合上HTTP/1.1に限定されるという話題があります。 FCMのAPIはHTTP/2に対応しているため、通信を多重化できます。これを使うと、まとめて複数人に通知するユースケースでは大幅な時間短縮が見込まれます。 しかしRubyのFCMクライアントでHTTP/2に対応しているものは見た感じ存在しないという問題がありました。既存のgemにPRを送る…
anatofuz.hatenablog.com
July 26, 2025 at 8:06 AM
https://anatofuz.hatenablog.com/entry/2025/07/25/190229
RubyでFCMのHTTPv1 APIをHTTP/2で扱うgem、ffccmmxがリリースされました。
HTTP/2対応により、複数人への通知が大幅に高速化されます。
多重送信機能やリトライ機能も備え、ActiveJobとの連携も容易です。
RubyでFCMのHTTPv1 APIをHTTP/2で扱うgem、ffccmmxがリリースされました。
HTTP/2対応により、複数人への通知が大幅に高速化されます。
多重送信機能やリトライ機能も備え、ActiveJobとの連携も容易です。
Ruby’s great, I recently implemented the async pattern for my activejob that manages chats could stream responses. I did not realize it was so performant, now I’ve got all sorts of ideas for performant cycles in ETL scenarios.. paolino.me/async-ruby-i...
Async Ruby is the Future of AI Apps (And It’s Already Here)
How Ruby's async ecosystem transforms resource-intensive LLM applications into efficient, scalable systems - without rewriting your codebase.
paolino.me
July 9, 2025 at 11:25 PM
Ruby’s great, I recently implemented the async pattern for my activejob that manages chats could stream responses. I did not realize it was so performant, now I’ve got all sorts of ideas for performant cycles in ETL scenarios.. paolino.me/async-ruby-i...
TDD for AI agents
"They wrote tests first, defined a clear schema for expected data, and made tweaks to get more consistent results. They also used ActiveJob::Performs to handle background jobs easily."
"They wrote tests first, defined a clear schema for expected data, and made tweaks to get more consistent results. They also used ActiveJob::Performs to handle background jobs easily."
July 5, 2025 at 9:19 PM
TDD for AI agents
"They wrote tests first, defined a clear schema for expected data, and made tweaks to get more consistent results. They also used ActiveJob::Performs to handle background jobs easily."
"They wrote tests first, defined a clear schema for expected data, and made tweaks to get more consistent results. They also used ActiveJob::Performs to handle background jobs easily."
Sidekiq workerとして実装した非同期ジョブクラス10個くらいを、ActiveJobのAPIに書き換える作業をGitHub Copilot Agentでやってもらい中。
楽なのはいいけど、こればかりやるようになったら明らかにコードを読む力というか体力は衰えそう。
楽なのはいいけど、こればかりやるようになったら明らかにコードを読む力というか体力は衰えそう。
May 31, 2025 at 1:32 PM
Sidekiq workerとして実装した非同期ジョブクラス10個くらいを、ActiveJobのAPIに書き換える作業をGitHub Copilot Agentでやってもらい中。
楽なのはいいけど、こればかりやるようになったら明らかにコードを読む力というか体力は衰えそう。
楽なのはいいけど、こればかりやるようになったら明らかにコードを読む力というか体力は衰えそう。
With the announcement (and merge) of ActiveJob::Continuation, it is a perfect time to announce that my pilot for AcidicJob Pro is finally ready for the first 5 companies/agencies that reach out. If you need ActiveJob::Continuation++ with extra tooling and observabikity, HMU!
May 30, 2025 at 6:57 PM
With the announcement (and merge) of ActiveJob::Continuation, it is a perfect time to announce that my pilot for AcidicJob Pro is finally ready for the first 5 companies/agencies that reach out. If you need ActiveJob::Continuation++ with extra tooling and observabikity, HMU!
I am working on a project and evaluating ActiveJob PG backends. Deep Research did a quick summary of Solid Queue, Good Job, and Delayed.
docs.google.com/document/d/1...
docs.google.com/document/d/1...
Evaluating ActiveJob Backends for PostgreSQL (Public)
Evaluating ActiveJob Backends for PostgreSQL: Solid Queue, Good Job, and Delayed Job I. Introduction A. The Role of Background Jobs in Modern Rails Applications In contemporary Ruby on Rails applicati...
docs.google.com
May 21, 2025 at 1:50 PM
I am working on a project and evaluating ActiveJob PG backends. Deep Research did a quick summary of Solid Queue, Good Job, and Delayed.
docs.google.com/document/d/1...
docs.google.com/document/d/1...
Join Chad and Kasper today for some live coding on a real Rails feature - using ChatGPT to fetch structured company data for a CRM. They’ll show how to set it up with ActiveJob::Performs and talk through the design decisions. https://www. youtube.com...
| Details | Interest | Feed |
| Details | Interest | Feed |
Origin
thoughtbot.social
May 8, 2025 at 1:49 PM
Join Chad and Kasper today for some live coding on a real Rails feature - using ChatGPT to fetch structured company data for a CRM. They’ll show how to set it up with ActiveJob::Performs and talk through the design decisions. www.youtube.com/watch?v=MLT_...
Building a Rails Feature with AI and ActiveJob
Chad is joined by Rails developer Kasper Timm Hansen as they pair on a real feature in a Rails app: using ChatGPT to generate structured data about companies...
www.youtube.com
May 8, 2025 at 1:44 PM
Join Chad and Kasper today for some live coding on a real Rails feature - using ChatGPT to fetch structured company data for a CRM. They’ll show how to set it up with ActiveJob::Performs and talk through the design decisions. www.youtube.com/watch?v=MLT_...
Join Chad and Kasper tomorrow as they pair on a real Rails feature and use ChatGPT to fetch structured company data for a CRM. They’ll show how to set it up with ActiveJob::Performs and talk through the design decisions. https://www. youtube.com/watc...
| Details | Interest | Feed |
| Details | Interest | Feed |
Origin
thoughtbot.social
May 7, 2025 at 9:13 PM
Join Chad and Kasper tomorrow as they pair on a real Rails feature and use ChatGPT to fetch structured company data for a CRM. They’ll show how to set it up with ActiveJob::Performs and talk through the design decisions. https://www. youtube.com/watc...
| Details | Interest | Feed |
| Details | Interest | Feed |
Origin
thoughtbot.social
May 7, 2025 at 9:13 PM
Join Chad and Kasper tomorrow as they pair on a real Rails feature and use ChatGPT to fetch structured company data for a CRM. They’ll show how to set it up with ActiveJob::Performs and talk through the design decisions. www.youtube.com/watch?v=MLT_...
Building a Rails Feature with AI and ActiveJob
Chad is joined by Rails developer Kasper Timm Hansen as they pair on a real feature in a Rails app: using ChatGPT to generate structured data about companies...
www.youtube.com
May 7, 2025 at 9:11 PM
Join Chad and Kasper tomorrow as they pair on a real Rails feature and use ChatGPT to fetch structured company data for a CRM. They’ll show how to set it up with ActiveJob::Performs and talk through the design decisions. www.youtube.com/watch?v=MLT_...
TIL about ActiveJob Callbacks, so my background jobs can call other background jobs. It's background jobs all the way down.
May 6, 2025 at 9:30 AM
TIL about ActiveJob Callbacks, so my background jobs can call other background jobs. It's background jobs all the way down.
RailsのGlobal IDとは何者なのかについて調べる🔍
はじめに ことの発端 業務でHogeJob.perform_later(user)のようなコードを書いていると、Jobの実行時には引数にオブジェクトを渡すのではなく、HogeJob.perform_later(use.id)という風に「オブジェクトのidを渡す使い方がベストプラクティスではないか？」という指摘をもらいました。 ActiveJobのアダプタとしてSidekiqを使っていたので、sidekiqのBestPracticesを調べてみると下記のようのことが書かれていました。 Sidekiq persists the…
はじめに ことの発端 業務でHogeJob.perform_later(user)のようなコードを書いていると、Jobの実行時には引数にオブジェクトを渡すのではなく、HogeJob.perform_later(use.id)という風に「オブジェクトのidを渡す使い方がベストプラクティスではないか？」という指摘をもらいました。 ActiveJobのアダプタとしてSidekiqを使っていたので、sidekiqのBestPracticesを調べてみると下記のようのことが書かれていました。 Sidekiq persists the…
RailsのGlobal IDとは何者なのかについて調べる🔍
はじめに ことの発端 業務でHogeJob.perform_later(user)のようなコードを書いていると、Jobの実行時には引数にオブジェクトを渡すのではなく、HogeJob.perform_later(use.id)という風に「オブジェクトのidを渡す使い方がベストプラクティスではないか？」という指摘をもらいました。 ActiveJobのアダプタとしてSidekiqを使っていたので、sidekiqのBestPracticesを調べてみると下記のようのことが書かれていました。 Sidekiq persists the arguments to perform_asy... Source link
inmobilexion.com
April 28, 2025 at 12:07 AM
RailsのGlobal IDとは何者なのかについて調べる🔍
はじめに ことの発端 業務でHogeJob.perform_later(user)のようなコードを書いていると、Jobの実行時には引数にオブジェクトを渡すのではなく、HogeJob.perform_later(use.id)という風に「オブジェクトのidを渡す使い方がベストプラクティスではないか？」という指摘をもらいました。 ActiveJobのアダプタとしてSidekiqを使っていたので、sidekiqのBestPracticesを調べてみると下記のようのことが書かれていました。 Sidekiq persists the…
はじめに ことの発端 業務でHogeJob.perform_later(user)のようなコードを書いていると、Jobの実行時には引数にオブジェクトを渡すのではなく、HogeJob.perform_later(use.id)という風に「オブジェクトのidを渡す使い方がベストプラクティスではないか？」という指摘をもらいました。 ActiveJobのアダプタとしてSidekiqを使っていたので、sidekiqのBestPracticesを調べてみると下記のようのことが書かれていました。 Sidekiq persists the…
One thing I'll say, Rails has a ton of good stuff in it. I think ActiveRecord is really well done, ActionController is pretty good, and ActiveJob is OK.
I think the front-end is an insanely complicated, creaky mess... with the exception of Turbo.
Oh and Rails CLI drives me crazy.
I think the front-end is an insanely complicated, creaky mess... with the exception of Turbo.
Oh and Rails CLI drives me crazy.
April 18, 2025 at 8:04 PM
One thing I'll say, Rails has a ton of good stuff in it. I think ActiveRecord is really well done, ActionController is pretty good, and ActiveJob is OK.
I think the front-end is an insanely complicated, creaky mess... with the exception of Turbo.
Oh and Rails CLI drives me crazy.
I think the front-end is an insanely complicated, creaky mess... with the exception of Turbo.
Oh and Rails CLI drives me crazy.