Hey,
I recently created a TYPO3 extension that integrates enqueue into TYPO3 ecosystem.
The advantage of this library is, that it supports multiple backends (RabbitMQ, Beanstalkd, and so on).
It's not completely ready and has some missing features, but it should not be much effort to integrate these features.
As far as i see, we need to replace the tx_mksearch_service_internal_Index::triggerQueueIndexing and all logic which produces the jobs.
We could provide a standard backend (for example Database or Filesystem) and a developer could override it, so he could use RabbitMQ or Redis for example.
if (!is_array($GLOBALS['TYPO3_CONF_VARS']['EXTENSIONS']]['t3queue']['mksearch'])) {
$GLOBALS['TYPO3_CONF_VARS']['EXTENSIONS']]['t3queue']['mksearch']['backend'] = 'amqp://localhost:5367';
}
Hey,
I recently created a TYPO3 extension that integrates enqueue into TYPO3 ecosystem.
The advantage of this library is, that it supports multiple backends (RabbitMQ, Beanstalkd, and so on).
It's not completely ready and has some missing features, but it should not be much effort to integrate these features.
As far as i see, we need to replace the
tx_mksearch_service_internal_Index::triggerQueueIndexingand all logic which produces the jobs.We could provide a standard backend (for example Database or Filesystem) and a developer could override it, so he could use RabbitMQ or Redis for example.