Laravel Command Bus Laravel Package

Product Decisions This Supports

• Architecture choices: Evaluate adopting a command bus pattern (CQRS-lite) to decouple business logic from controllers and enable async processing via AMQP.
• Build vs. buy: Decide whether to use this package versus building custom command dispatching and AMQP integration in-house.
• Observability roadmap: The new debug option for AMQP logging supports decisions about investing in operational visibility and faster incident resolution.
• Use case prioritization: Identify features that benefit from async command handling (e.g., order processing, notifications, report generation) and assess package fit.
• Upgrade planning: Minor version bump (v1.1.7 → v1.1.8) with no breaking changes; low risk to adopt for debugging needs.

When to Consider This Package

• You are building a Laravel application and want a lightweight command bus with AMQP (RabbitMQ) support.
• Your team follows CQRS or command-handler patterns and needs a simple integration layer.
• You require configurable debug logging for AMQP message flows to troubleshoot async command failures.
• You prefer a small, focused package over a larger framework (e.g., Symfony Messenger, Laravel Horizon for Redis queues).
• Look elsewhere if: you are not on Laravel, need multi-transport support beyond AMQP, require enterprise-grade monitoring, or need a more mature/actively maintained package with broader community adoption. Also avoid if you need built-in retry/dead-letter policies beyond what AMQP provides natively.

How to Pitch It (Stakeholders)

• Executives: This package lets us adopt a proven command bus pattern with minimal custom code, reducing time-to-market for async features. The new debug logging improves operational reliability and cuts troubleshooting time, lowering support costs.
• Engineering: A Laravel-native command bus with AMQP integration that now includes optional debug logging for AMQP—useful for diagnosing message dispatch issues in staging and production. It’s a small, focused dependency (v1.1.8) with no breaking changes, so we can trial it in a bounded service before wider rollout.