zaber-dev/laravel-context
A lightweight Laravel package for managing shared application context. Store and retrieve contextual data such as request metadata, tenant details, or user settings across middleware, services, and views without passing it manually.
Laravel Context v1.0.0 is the first stable release of an ambient execution-context and boundary-propagation package for Laravel. It is positioned as infrastructure for carrying request/job-scoped context across models, queues, cache, storage, logging, events, routing, and validation. For a TPM, the package is most valuable when the organization is already paying the complexity cost of manually passing tenant IDs, correlation IDs, actor IDs, or request metadata through multiple Laravel subsystems.
Architecture fit: Good fit for Laravel applications that need consistent context propagation for multi-tenancy, audit trails, request tracing, feature targeting, or operational metadata. It is not a full tenancy or observability platform; it is a propagation layer. It should be evaluated as shared infrastructure, not a feature-level utility. The cross-boundary scope is the main architectural benefit and the main risk: implicit context reduces boilerplate but creates hidden coupling if context lifecycle is not rigorously defined.
Integration feasibility: Likely feasible for a standard Laravel application via Composer and service-provider registration, but the release notes do not provide the compatibility matrix, configuration surface, or lifecycle hooks. Integration risk is moderate until the team verifies supported Laravel/PHP versions, queue serialization behavior, cache/storage key scoping, logging redaction, and long-running worker behavior. Because this is a first stable release, treat the API as stable enough to pilot but not yet proven across diverse production workloads.
Technical risk: The primary risk is context leakage or loss across boundaries: request-to-queue, queue-to-worker, Octane/Swoole long-running processes, nested jobs, event listeners, and validation/routing boundaries. Secondary risks include oversized serialized context in queue payloads, cache-key cardinality and collisions, storage-path isolation errors, sensitive data exposure in logs, and performance overhead from pervasive context access. The package’s value depends on deterministic set/clear/reset semantics and strong test helpers. Vendor maturity, maintainer responsiveness, documentation depth, and security posture are unknown from the release note alone.
Key questions:
Stack fit: Best suited to Laravel applications with cross-cutting context needs: multi-tenant SaaS, regulated audit logging, distributed tracing correlation, queue-heavy workloads, or large teams standardizing request metadata. It is less compelling for small applications or teams already served by a mature tenancy/observability stack with explicit context passing.
Migration path: Start with a bounded pilot rather than a platform-wide rollout. Inventory existing context sources and manual propagation points, define a minimal context schema, and map each supported boundary to a business need. Pilot first on request middleware plus logging and queue propagation, then expand to cache, storage, events, routing, and validation only after the lifecycle semantics are proven. Maintain a rollback path by keeping existing explicit context paths until the package demonstrates parity.
Compatibility: Validate against the organization’s actual Laravel/PHP matrix, queue driver, cache store, filesystem driver, logging channels, and worker runtime. Pay special attention to Octane/Swoole, Horizon, job serialization, and any existing tenancy or tracing middleware. Confirm whether the package is additive or requires replacing existing context plumbing.
Sequencing: First perform dependency and security review. Second, run a technical spike covering request-to-job propagation, context reset in long-running workers, log redaction, and cache/storage isolation. Third, pilot in one non-critical service with explicit success criteria: no context bleed, no missing job context, acceptable overhead, and debuggable behavior. Fourth, codify conventions and tests before expanding to production-critical paths.
Maintenance: Adds a new infrastructure dependency with a v1 API. TPM should assign ownership, track upstream releases, and require a documented upgrade and rollback plan. Because this is the first stable release, expect possible early patch releases and API refinement.
Support: Teams will need runbooks for context inspection, missing-context debugging, queue replay behavior, and incident response for cross-tenant or cross-request contamination. Documentation quality and upstream support responsiveness should be validated before broad adoption.
Scaling: Context propagation adds per-request and per-job overhead and can increase queue payload size and cache-key cardinality. Storage and logging isolation must scale with tenant/context count. Long-running workers require strict reset semantics to prevent context accumulation across jobs.
Failure modes: The highest-severity failures are context bleed between tenants or requests, silent context loss in queued jobs, cache or storage isolation errors, sensitive data in logs, and propagation failures in events or validation. These should be treated as production risks requiring automated tests and monitoring, not just code-review concerns.
Ramp-up: Laravel developers should ramp up quickly on basic usage, but correct lifecycle handling across queues, workers, and cache/storage boundaries requires deliberate enablement. TPM should fund a short internal spike, publish context conventions, and add a review checklist covering set/clear behavior, serialization, redaction, and boundary-specific tests.
How can I help you explore Laravel packages today?