https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41506
--- Comment #6 from David Cook <[email protected]> --- I'm on the fence (surprise surprise). I don't think that I feel strongly one way or another anymore, but I've got some thoughts (not quite pros/cons) below if you want to read them. -- I haven't used the SQL polling method for the background workers, so I don't know how effective/efficient it is or how well it supports multiple workers for 1 queue, but I have heard that a lot of people like it. I also have used SQL polling for background jobs in the past and it was good enough for simple use cases. Originally, I had an interest in RabbitMQ for high performance background jobs, as I was targeting background jobs that needed to be actioned extremely quickly (ie near real-time) and needed a FIFO queue that could ensure proper distribution of tasks to multiple concurrent workers. However, the use case for that was never realised in Koha, so it didn't matter in the end. Despite a few hiccups, RabbitMQ has worked pretty well for me in Koha (and on other systems). I think there have been times where people have avoided RabbitMQ rather than engaging with it for fixing bugs. But... I think that's also a sign that maybe RabbitMQ isn't a good fit for the Koha community. If an alternative solution has grown up in reaction to it, maybe we need to listen to that. There's also the issue with RabbitMQ not being very easy to upgrade. We don't have a lot of resources in the Koha community, and supporting multiple options can be difficult. We already do it with Zebra/Elasticsearch and that's hard enough. Anyway, maybe I'll leave it there for now. Basically, I think RabbitMQ provides us with a lot of power and potential to carry Koha into the future. However, I also acknowledge that a lot of people don't like it and don't want it in Koha, and maybe it's overkill for what we need in Koha at present. When making choices on technology, I think we do need to think about what we can collectively maintain as a community. It does seem like we have more human resources for maintaining the SQL polling option than the RabbitMQ option. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
