Stomp Laravel Package

Product Decisions This Supports

• Asynchronous Processing & Microservices Architecture: Enables decoupled communication between services (e.g., order processing, notifications, or background jobs) via STOMP, reducing direct API calls and improving scalability.
• Hybrid Queue Infrastructure: Supports integration with Apache ActiveMQ, RabbitMQ, or other STOMP-compatible brokers, allowing teams to avoid vendor lock-in while leveraging existing messaging infrastructure.
• Roadmap for Event-Driven Systems: Critical for building event sourcing, CQRS, or real-time systems (e.g., chat apps, IoT data pipelines) where low-latency message passing is required.
• Build vs. Buy: Buy—avoids reinventing STOMP protocol support, reducing dev time and maintenance overhead. Only consider building if needing custom STOMP extensions or proprietary optimizations.
• Use Cases:
  • High-throughput job queues (e.g., image processing, PDF generation).
  • Cross-service communication in polyglot architectures (PHP + Java/Node.js services).
  • Replacing RabbitMQ-specific libraries with a protocol-agnostic alternative.

When to Consider This Package

• Adopt if:
  • Your stack already uses STOMP-compatible brokers (ActiveMQ, RabbitMQ, etc.) and you need a PHP-friendly queue client.
  • You require Queue Interop compliance for interoperability with other languages/frameworks.
  • Your team prioritizes MIT-licensed, actively maintained (via Forma-Pro) open-source tools.
  • You need Guzzle HTTP adapter support for advanced broker management (e.g., monitoring via RabbitMQ API).
• Look elsewhere if:
  • Your broker doesn’t support STOMP (e.g., AWS SQS, Azure Service Bus—use enqueue/sqs or enqueue/azure-service-bus instead).
  • You need zero-configuration simplicity (consider enqueue/amqp-ext for RabbitMQ-specific optimizations).
  • Your team lacks PHP 8.1+ or Composer dependency management experience.
  • You require exactly-once delivery semantics (STOMP alone may need additional transaction handling; evaluate enqueue/doctrine for DB-backed durability).

How to Pitch It (Stakeholders)

For Executives: "This package lets us use existing STOMP brokers (like RabbitMQ) to decouple services, reducing latency and improving scalability—without building or maintaining custom queue logic. It’s MIT-licensed, backed by Forma-Pro (a Symfony specialist), and integrates seamlessly with our PHP stack. For example, we could offload order processing to a background queue, cutting API response times by 50% while handling spikes in traffic. The cost? Minimal—just a Composer dependency and basic config."

For Engineering: *"The enqueue/stomp package gives us a standardized, interoperable way to send/receive messages via STOMP, with support for:

• Queue Interop: Works with any STOMP broker (ActiveMQ, RabbitMQ, etc.).
• Guzzle HTTP: Enables broker management (e.g., monitoring queues via RabbitMQ API).
• PHP 8.1+: Modern tooling with type safety.
• Zero Lock-in: Swap brokers without rewriting queue logic. Tradeoff: Slightly more setup than broker-specific clients, but worth it for flexibility. **Recommended for async jobs, event-driven workflows, or microservices needing cross-language messaging."

For Architects: *"This fills a gap in our queue strategy by providing a protocol-agnostic STOMP transport that:

1. Avoids vendor lock-in (unlike RabbitMQ-specific libraries).
2. Aligns with Queue Interop for future-proofing.
3. Leverages existing brokers (no new infrastructure needed). Use it for: Background processing, event streaming, or service-to-service comms where STOMP is already deployed. Pair with enqueue/doctrine for persistence if needed."*