[Koha-bugs] [Bug 25245] Add a plugin hook to allow running code on a nightly basis

[bugzilla-daemon at bugs.koha-community.org]

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25245

--- Comment #26 from David Cook <dcook at prosentient.com.au> ---
(In reply to Tomás Cohen Arazi from comment #23)
> (In reply to Kyle M Hall from comment #22)
> > (In reply to Jonathan Druart from comment #21)
> > > I have the feeling that this should have been implemented on top of bug
> > > 22417 (with bug 1993 in mind).
> > 
> > Is there any reason this cannot be updated to use the functionality of those
> > bugs once they've been taken care of? It doesn't look like there is a
> > definite end in site for them.
> 
> I agree here. Bug 22417 is a longer shot IMHO.

I agree with everyone in a way.

I've spent years talking about and working on task scheduler functionality for
Koha, and I don't think it's happening any time soon. Cron is a
well-established familiar task scheduler that can do a good enough job. 

I'd argue Bug 22417 tries to be too comprehensive, and that we'd be better off
just adding RabbitMQ and Net::Stomp as dependencies, and then doing a light
experimental implementation here. However, even if we had only 1 worker
consuming from RabbitMQ, that's another process to manage. It adds new
administrative overhead and fragility that we don't have by continuing to use
cron.

Frido also made a good point back in Portland about queue based task schedulers
(like the one I wrote). From a vendor point of view, you might not want all
your Koha instances running their background jobs at the same time. If those
background jobs use APIs, you might end up hitting rate limits for instance. Or
if you're sending out lots of emails, you might get flagged as a spammer. So it
becomes prudent for vendors to be able to stagger background jobs on a server.

Of course, that criticism applies to using cron.daily for background jobs too.

-- 
You are receiving this mail because:
You are watching all bug changes.