Bitrix Framework introduced a message queue mechanism starting from version 25.100.300 of the main module. This feature enables asynchronous processing, allowing background tasks to execute independently of the user's primary request. This approach prevents delays caused by slow external services or temporary service unavailability.
The system architecture consists of a message, a queue, a broker, a worker, and a handler. Messages contain data for background operations, while the broker stores these messages in a database. The framework currently supports a 'db' type broker. Workers retrieve messages from the broker and pass them to the designated handler for execution.
Developers can generate message classes using the 'make:message' command, available since version 25.900.0. Handlers are created via the 'make:messagehandler' command. The queue configuration is defined in the module's '.settings.php' file, linking specific queues to their respective handlers.
Global settings are managed in the '/bitrix/.settings.php' file, where developers specify the execution mode and broker parameters. The 'cli' mode allows for manual processing via the 'messenger:consume' command. This setup ensures that tasks like calendar synchronization are handled reliably in the background.
