You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I wanted to write this out, mainly for my own thinking. And would love any feedback input on it.
The general plan that I have imagined in v3 is:
Extracting and centralizing the Scheduler/Notifier/Poller/CronManager instances inside of a global (e.g. GoodJob.manager). Currently they either are loose inside of the CLI, or within individual adapters. Queue and thread configuration is global, so there should only be one set of these in the process.
Extracting the majority of the logic from Adapter#enqueue, and moving that up to the global GoodJob.enqueue level (or maybe GoodJob::Job.enqueue or GoodJob::Execution.enqueue?). That reduces the size of the adapter, and unlocks...
Creating something like GoodJob.bulk_enqueue for enqueuing multiple jobs at once. This isn't possible while all of the enqueue logic lives within the Adapter (because an application/jobs can have multiple GoodJob adapters). That unlocks...
The cleaner interface for Batches with block enqueue (e.g. batch.jobs { SomeJob.perform_later; OtherJob.perform_later }
The text was updated successfully, but these errors were encountered:
I wanted to write this out, mainly for my own thinking. And would love any feedback input on it.
The general plan that I have imagined in v3 is:
GoodJob.manager
). Currently they either are loose inside of the CLI, or within individual adapters. Queue and thread configuration is global, so there should only be one set of these in the process.Adapter#enqueue
, and moving that up to the globalGoodJob.enqueue
level (or maybeGoodJob::Job.enqueue
orGoodJob::Execution.enqueue
?). That reduces the size of the adapter, and unlocks...GoodJob.bulk_enqueue
for enqueuing multiple jobs at once. This isn't possible while all of the enqueue logic lives within the Adapter (because an application/jobs can have multiple GoodJob adapters). That unlocks...batch.jobs { SomeJob.perform_later; OtherJob.perform_later }
The text was updated successfully, but these errors were encountered: