Details
-
Improvement
-
Resolution: Workaround exists
-
Major
-
None
-
None
-
None
-
None
Description
The current RabbitMQ modules use a single queue for all activations. This means that (as opposed to the magnolia standard activation process):
- no concurrent activations are possible
- a «single point of failure» is added to the activation process. If the queue ist blocked / corrupted for some reason, activations are blocked on a global level until you fix the problem (which can take time and therefore lead to even more issues, e.g. run-up of messages that lead to RabbitMQ memory problems, etc.).
Adding support for concurrent activations might not be trivial. But for multi-site installations, it should be easy to add multi-queue support (one queue per site). This would make concurrent activations possible on per-site basis and also limit activation problems to particular sites.
Checklists
Acceptance criteria