Service queue

Service Queue provides a provider-neutral API and configuration framework for publishing messages to external queue services. It allows Drupal modules to send work to remote messaging platforms without being tied to a specific transport implementation.

Features

Service Queue provides a reusable foundation for asynchronous processing and event-driven integrations.

Features include:

• Provider-neutral queue connection configuration.
• Standard API for publishing messages to remote queues.
• Transport-independent architecture.
• Pluggable transport provider system.
• Support for authenticated queue communications.
• Reusable configuration entities for queue connections.
• Developer-friendly service APIs.
• Designed for enterprise integration and automation scenarios.

Typical use cases include:

• Publishing business events to external systems.
• Asynchronous processing of Drupal workflows.
• Integrating Drupal with cloud messaging platforms.
• Sending work items to downstream applications.
• Decoupling user-facing actions from background processing.
• Building scalable event-driven architectures.

Post-Installation

After installing and enabling the module:

1. Install and enable a queue transport provider.
2. Create any provider-specific connection required by the selected transport.
3. Navigate to Configuration > Queue connections.
4. Create a queue connection.
5. Select the provider connection.
6. Specify the target queue name.
7. Enable the queue connection.

Service Queue does not directly connect to queue platforms. Instead, transport modules provide the implementation required to communicate with a specific queue service.

Additional Requirements

Required:

• Drupal 11
• At least one transport provider module

Examples of transport providers include:

• Service Bus Provider
• Custom queue transport implementations

A transport provider is required because Service Queue defines the API and configuration framework but does not implement a queue transport itself.

Recommended Modules/Libraries

Service Queue is designed to work alongside:

• OAuth Provider for authentication to external services.
• Mailbox Provider for processing inbound email workflows.
• Service Bus Provider for Azure Service Bus integration.
• Custom automation and workflow modules.
• Enterprise integration solutions.

Together these modules enable Drupal to receive information from external services, process it, and publish resulting events or work items to remote queue systems.

Similar Projects

Drupal provides several queue-related APIs and modules, but many are focused on internal queue processing within Drupal.

Service Queue focuses on a different problem: publishing authenticated messages to external queue platforms through a common provider interface.

The provider architecture allows transport implementations to be added without changing the consuming application code. This makes it easier to switch or support multiple queue technologies while maintaining a consistent Drupal API.

Supporting this Module

Issues, bug reports, feature requests, and merge requests are welcome through the Drupal.org issue queue.

Community feedback helps improve interoperability with additional queue providers and enterprise integration scenarios.

Community Documentation

Documentation currently includes:

• Installation and configuration guidance.
• Queue connection setup instructions.
• Developer examples for publishing messages.
• Provider integration guidance.
• Authentication provider extension examples.

Additional tutorials, reference implementations, and architecture examples will be added as the project evolves.

Developer Notes

Service Queue exposes a queue management service that allows modules to publish structured payloads without requiring knowledge of the underlying transport implementation. Transport providers implement the queue delivery mechanism, while authentication providers can supply provider-specific authentication workflows.

This separation of concerns allows developers to build integrations once and deploy them across different queue technologies through interchangeable transport providers.