Enqueue Laravel Package

Product Decisions This Supports

• Unified Messaging Architecture: Enables a single abstraction layer for AMQP, Redis, and SQS, reducing complexity and vendor lock-in for Laravel applications scaling into microservices or event-driven systems. Aligns with roadmaps for asynchronous workflows (e.g., background jobs, sagas, event sourcing) without framework-specific constraints.
• Build vs. Buy Decision: Avoids reinventing a messaging abstraction layer, saving development time while maintaining flexibility. Ideal for teams already using Enqueue or Ecotone but needing custom transports (e.g., Stomp, Beanstalkd) or multi-broker support.
• Laravel Integration: Supports asynchronous communication (e.g., decoupled services, horizontal scaling) while leveraging Laravel’s ecosystem. Use cases include:
  • Decoupling services (e.g., order processing → payment → notification).
  • Scaling consumers (e.g., Redis for high throughput, SQS for serverless).
  • Hybrid architectures (e.g., mixing AMQP for real-time with SQS for serverless).
• Incremental Adoption: Ecotone’s declarative PHP 8 attributes (e.g., #[CommandHandler]) allow teams to start with simple commands and later adopt advanced patterns (e.g., sagas, outbox) without rewrites. Reduces risk for Laravel teams unfamiliar with DDD/CQRS.
• Future-Proofing: Designed to scale from simple queueing to distributed messaging, making it suitable for long-term Laravel projects with evolving async requirements.

When to Consider This Package

• Adopt when:

  • Your Laravel application requires multi-broker support (AMQP, Redis, SQS) with shared lifecycle management (channels, consumers).
  • You need to integrate custom transports (e.g., Stomp, Beanstalkd) into Laravel’s async workflows.
  • You’re building event-driven architectures (e.g., CQRS, event sourcing) and want to avoid framework-specific solutions.
  • Your team is already using Enqueue or Ecotone and seeks a unified abstraction layer for messaging.
  • You prioritize long-term maintainability over short-term simplicity, especially for greenfield projects or microservices.

• Look elsewhere if:

  • You only need basic queueing (e.g., Laravel’s built-in queues or Redis Streams) and don’t require Ecotone’s advanced features.
  • Your team lacks PHP/Enqueue expertise or familiarity with Ecotone’s architecture (DDD/CQRS patterns).
  • You’re constrained by low adoption risk (1 star, 0 dependents); prioritize for greenfield projects or niche use cases.
  • You need enterprise support (no commercial backing; community-driven).
  • Your Laravel app relies heavily on Horizon or native queue workers (php artisan queue:work), as Ecotone requires custom integration.

How to Pitch It (Stakeholders)

For Executives: "This package lets us standardize on a single messaging layer for AMQP, Redis, and SQS in Laravel, reducing operational overhead and future-proofing our async workflows. By leveraging Ecotone’s declarative PHP attributes, we can start with simple background jobs and scale to complex event-driven architectures—without rewrites. It’s a build vs. buy win: we avoid reinventing the wheel while keeping options open for custom brokers. Low risk for greenfield projects; ideal if we’re already using Enqueue or planning for microservices. The tradeoff is minimal upfront investment for long-term flexibility."

For Engineering: *"Ecotone’s Enqueue adapter gives us a shared transport layer for all our message brokers, so we can swap implementations (e.g., RabbitMQ → SQS) without changing business logic. Key benefits for Laravel:

• Unified consumers/channels: Manage lifecycle across brokers via Ecotone’s Bus.
• Custom transports: Extend to unsupported brokers (e.g., Stomp) with minimal effort.
• PHP 8 attributes: Clean syntax for commands/handlers (e.g., #[CommandHandler]), reducing boilerplate.
• Laravel-compatible: Works via Ecotone Lite (PSR-11) if we’re not tied to Symfony. Tradeoffs:
• Early-stage package (1 star), but critical if we’re betting on Ecotone long-term.
• Requires custom integration for Laravel’s queue:work (e.g., Supervisor/Kubernetes).
• Learning curve for Ecotone’s DDD/CQRS patterns if the team is new to them. Recommendation: Start with a proof-of-concept for a non-critical async workflow (e.g., notifications) to validate integration before full adoption."*