Drupal has solid queue support, but it's very much database based and expects consumers to be running within Drupal. If we latched onto the core queue system, or perhaps the advancedqueue module, we could get a better UI/Dashboard for the queue jobs. We also then would have the possibility to move our consumers from Java/Camel and into Drupal as Drush/Cron type stuff instead. This would help a lot when dealing with jobs that fail, b/c we'd have direct access to Drupal's logging mechanisms. It would also mean we could drop the few REST endpoints we have, since we can manipulate entities directly without the need for REST.
Drupal has solid queue support, but it's very much database based and expects consumers to be running within Drupal. If we latched onto the core queue system, or perhaps the advancedqueue module, we could get a better UI/Dashboard for the queue jobs. We also then would have the possibility to move our consumers from Java/Camel and into Drupal as Drush/Cron type stuff instead. This would help a lot when dealing with jobs that fail, b/c we'd have direct access to Drupal's logging mechanisms. It would also mean we could drop the few REST endpoints we have, since we can manipulate entities directly without the need for REST.