[Koha-bugs] [Bug 22417] Add a task queue

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

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

--- Comment #160 from Marcel de Rooy <m.de.rooy at rijksmuseum.nl> ---
(In reply to Jonathan Druart from comment #158)
> (In reply to Marcel de Rooy from comment #156)
> > And perhaps even more important and already commented on a bit, we are
> > adding a task queue here with a message queue. Obviously, we could send
> > other stuff into the MQ; so this might become a problem later on.
> > And sounding a bit nasty, but not meant to be: We are saving the data into a
> > background job table as well as sending it to MQ. Aren't we being redundant
> > here? Actually, it looks like our background job could just hook to the
> > background jobs table and process what is left there. So what is the real
> > benefit here in this implementation of the MQ exactly?
> 
> I am not sure I understand what you are suggesting.
> Do you mean misc/background_jobs_worker.pl could watch the DB table and so
> we could remove the RabbitMQ dependency?

No, that is not my suggestion here. But this argument is about its
architecture. We use a message queue for a more specific goal. This has
translated into the actual code making it harder to widen the scope again.
Later on, I want to add messages (no tasks) in another area but what if I dont
want to go via BackgroundJob?

The last few sentences actually ask for a justification why send we the same
data to both a table and the message queue. What is in this specific case the
added value of the message queue? If we only use it for this specific case, it
looks like much overhead for what it brings. If the justification is in the
wider use of a message queue, lets translate that to its design.

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