Bref Sqs Laravel Laravel Package

Product Decisions This Supports

• Serverless roadmap sequencing. This package is the glue that lets a Laravel app running on AWS Lambda (via Bref) use SQS as its queue backend — the piece that makes "scale-to-zero" web + async worker architecture viable. Its release cadence effectively sets the floor for when we can move off Bref 0.x onto Bref 1.x.
• Build vs. buy. The functionality is thin, well-understood wiring (queue driver + Lambda event-to-job bridging). Building it in-house is feasible but low-leverage; adopting this package is the cheaper path unless we need custom batching, FIFO semantics, or per-tenant queue routing that the package doesn't expose.
• Cost/architecture decisions. SQS-backed queues on Lambda remove always-on worker instances. This is an input to any decision to shrink EC2/ECS worker fleets or consolidate queue infrastructure onto AWS-native services.
• Use cases it unlocks or de-risks: async job processing on Lambda, fan-out workloads, bursty/event-driven pipelines, and offloading slow work from request paths without paying for idle workers.
• Dependency/compatibility governance. The 2.0.0 major bump is a signal for the upgrade calendar: it tells us the maintainer is tracking Bref 1.x, and it forces an explicit decision about which Bref major we standardize on across services.

When to Consider This Package

Adopt when:

• We run (or are committing to run) Laravel on AWS Lambda with Bref 1.x, and want SQS as the queue backend rather than a database or Redis queue.
• We want the standard Laravel dispatch() / queue worker experience preserved on a serverless runtime, with minimal custom code.
• We are planning a Bref 0.x → 1.x migration; this release is the compatible path, so it should be part of that upgrade plan rather than an afterthought.

Compatibility caveat for this release: the only stated change in 2.0.0 is added support for bref/bref 1.3.*. A major version number combined with a dependency-floor change strongly implies that earlier Bref lines (the 0.x series) are no longer supported. Treat this as a breaking dependency bump, not a feature addition: confirm the package's composer.json constraint before upgrading, and if any service is still on Bref 0.x, pin that service to the 1.x line of this package.

Look elsewhere when:

• The app runs on conventional servers/containers — Laravel's first-party SQS queue driver already covers this; this package adds nothing.
• We are standardized on a different serverless runtime (Vapor, Container Apps, Cloud Run) or on Redis/SQS-FIFO semantics this package doesn't model.
• We need active maintenance guarantees: this is a small, effectively single-maintainer package. If it sits on a critical path, budget for the possibility of forking or vendoring it.
• Observability requirements are strict (custom metrics, DLQ tooling, per-job tracing) and would require more instrumentation than the package provides.

How to Pitch It (Stakeholders)

To executives: This is a small open-source connector that lets our Laravel application run its background job processing on AWS Lambda with SQS queues instead of always-on worker servers. The practical upside is paying only for work actually performed and removing idle worker capacity — a direct infrastructure cost lever. The new 2.0.0 release aligns the package with the current generation of our serverless runtime (Bref 1.x), which is the prerequisite for that migration. Risk is low and contained: it's a thin, replaceable component, though it is maintained by a single author, so we should avoid making it a single point of failure for anything business-critical.

To engineering: 2.0.0 adds support for bref/bref 1.3.*. The major version bump indicates a compatibility break — assume Bref 0.x is no longer supported and verify the Composer constraint before merging. Recommended sequencing: upgrade Bref to 1.x first, then this package, then validate queue dispatch/consumption and failure/retry behavior on a non-production Lambda before rollout. If any service must remain on Bref 0.x, keep it pinned to this package's 1.x line; do not attempt a partial upgrade.