#activejob — Public Fediverse posts

:ruby: Isn’t defining a job class for each async execution unit too much boilerplate?

Let’s try to implement seamless async execution in Ruby, using ActiveJob and proxy objects!

https://kzone.winosx.com/posts/asynchronous-method-calls-using-rails-s-activejob

#Ruby #Rails #ActiveJob

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?

#rubyonrails #activejob #SolidQueue

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?

#rubyonrails #activejob #SolidQueue

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?

#rubyonrails #activejob #SolidQueue

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?

#rubyonrails #activejob #SolidQueue

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?

#rubyonrails #activejob #SolidQueue

Is there a document somewhere that explains what a new #rails #ActiveJob queue adapter should implement? An interface specification of sorts?

Seems I'll go read the code, then.