ddd-message-handler-specialist

Asynchronous background processing in a DDD PHP application is handled using the AppMessage/AppMessageHandler pattern with Symfony Messenger. This approach routes tasks outside the request lifecycle while maintaining auth context and structured logging.

Symfony Messenger propagates authentication context to background tasks by automatically passing the initiator's auth details to the asynchronous work. This ensures background handlers execute with consistent user permissions and workspace routing guards.

The best way to structure async message handlers in a DDD core is using standardized AppMessage and AppMessageHandler scaffolds. This pattern separates asynchronous task execution from the request lifecycle while enforcing consistent routing and error handling.

To wire Symfony Messenger transports for a new AppMessage, you create the message and handler classes, bind them to a specific transport, and configure a supervisor-based consumer workflow. This routes the task to the correct background processing queue.

A supervisor-based consumer workflow is needed for PHP async tasks to ensure robust consumption and error handling. It manages the background worker processes, keeping transport routing reliable when tasks execute outside the main request lifecycle.

Yes, the AppMessageHandler pattern supports tasks requiring workspace routing by implementing specific routing guards. It ensures background tasks are securely directed to the correct workspace with proper authentication context.