Product Decisions This Supports

Scaling read capacity without sacrificing consistency: Enables adoption of read/write database splits (read replicas) for performance, while ensuring that after a write, subsequent reads (even across requests) hit the primary for a configurable window—preventing stale reads that erode user trust.
Build vs. buy: Avoids building custom cross-request stickiness logic (cache-backed) on top of Laravel’s built-in per-request sticky option. The package is small, focused, and now explicitly supports Laravel 13/14 and PHP 8.5, reducing maintenance burden.
Feature and UX consistency: Critical for flows like profile updates, order placement, or inventory changes where a user must immediately see their own write. Product can confidently ship such features on a read-replica architecture.
Roadmap enabler: Supports a roadmap that includes horizontal read scaling or geographic read replicas without introducing eventual-consistency bugs in core user journeys.
Use cases: E-commerce checkout/order confirmation, SaaS account settings, social posting (write then immediate feed view), any CRUD app where “my change” must be visible instantly.

When to Consider This Package

You use Laravel with read/write connection configuration (read replicas) and observe stale reads after writes, especially when the write and subsequent read happen in different requests.
You need stickiness that outlives a single request (Laravel’s native sticky is per-request only) and are comfortable using your cache store to track recent writes.
Your consistency requirements are “read-your-writes” for a short TTL (e.g., a few seconds), not full ACID across replicas.
You want a maintained, lightweight package rather than custom middleware or event listeners.
Look elsewhere if: you run a single database (no replicas), require synchronous replication or strong consistency guarantees beyond a TTL, or cannot accept cache dependency for correctness. Also consider alternatives if you need database-agnostic stickiness across non-Laravel services.

Executives: This package lets us scale reads with replicas without users seeing stale data after they make changes—protecting conversion, trust, and support costs. It’s a small, actively maintained dependency that now supports upcoming Laravel 14 and PHP 8.5, so it won’t block our upgrade roadmap.
Engineering: Drop-in solution for cross-request read-after-write consistency on read/write split setups. v2.2.1 confirms CI coverage for PHP 8.5 and composer constraints for Laravel 14 (with Laravel 13 documented), so it’s future-proof and low-risk to adopt. No breaking changes; integrate via cache-backed stickiness with a configurable TTL.