Product Decisions This Supports

Feature enablement: The new header support in v1.1 allows teams to attach metadata (e.g., correlation IDs, tenant IDs, retry hints, routing keys) to enqueued messages without custom serialization or workarounds. This directly enables observability, distributed tracing, and multi-tenant queue isolation.
Roadmap acceleration: Product can now plan features that depend on message-level metadata—such as per-tenant dead-letter routing, A/B test cohort tagging in async jobs, or priority lanes—without building a bespoke enqueue layer.
Build vs. buy: If the product needs message headers for routing or tracing, this package removes the need to build and maintain custom queue abstraction. The cost of adoption is low (Laravel-native, minor version bump), while the cost of building equivalent header support in-house is non-trivial (serialization, broker compatibility, testing).
Use cases: Event-driven integrations, asynchronous job processing with traceability, multi-tenant SaaS where messages must carry tenant context, and any workflow requiring header-based filtering or routing at the broker level.

When to Consider This Package

Adopt when: You are on Laravel, need to enqueue messages to a broker (e.g., SQS, RabbitMQ, Redis), and require message headers for tracing, routing, or tenant isolation. The v1.1 release is a minor, non-breaking addition—safe to adopt if you already use the package or are evaluating it for header-dependent features.
Look elsewhere when: You need advanced broker features beyond headers (e.g., complex topic exchanges, exactly-once semantics, transactional outbox), you are not using Laravel, or you require a fully managed queue abstraction with built-in schema registry. Also consider alternatives if header support must be paired with strict ordering guarantees that this package does not document.

Executives: This minor release adds header support to enqueued messages, unlocking observability, multi-tenant routing, and tracing capabilities with minimal engineering effort. It reduces time-to-market for async features and avoids costly custom queue infrastructure—low risk, high leverage.
Engineering: v1.1 is a non-breaking feature addition that lets you attach headers to messages at enqueue time. Use it to propagate correlation IDs, tenant context, and routing metadata without custom serialization. Integration is straightforward for Laravel teams; no migration is required beyond upgrading the package.