Bug 41506 - Should we remove RabbitMQ?
Summary: Should we remove RabbitMQ?
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Architecture, internals, and plumbing (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-12-31 12:51 UTC by Katrin Fischer
Modified: 2025-12-31 17:18 UTC (History)
1 user (show)

See Also:
GIT URL:
Initiative type: ---
Sponsorship status: ---
Comma delimited list of Sponsors:
Crowdfunding goal: 0
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Katrin Fischer 2025-12-31 12:51:14 UTC
At the hackfest in Wellington this came up as a question in the discussion and it was decided to bring it up at the next development meeting. 

https://koha-hedgedoc.servers.llownd.net/Development_IRC_meeting_26_November_2025#

The discussion is difficult and we want to include as many opinions/people as possible. I felt it would be a bit lost on bug 35920, so proposing a separate bug report instead.
Comment 1 Katrin Fischer 2025-12-31 12:56:53 UTC
Adding some more personal notes:

* When we had a survey at the hackfest in Marseille last year it showed that almost all of the big providers have deactivated RabbitMQ in their installations. That certainly impacts the amount of testing and development work in that area.

* Currently RabbitMQ is a dependency that is installed with the Koha packages. So currently it requires some hacking to make sure it's not installed and running even when the new pref JobsNotificationMethod is set to SQL polling. 

I'll link open RabbitMQ related bugs in the see also section.