- Is tempest/kv-store a Laravel package?
- No. It is a read-only sub-split of the kv-store component from the Tempest framework ecosystem, published by tempestphp, not a Laravel package. It overlaps with Laravel only at the PHP and Composer level. Installing it does not give you a Laravel cache driver, and the assessment notes near-total functional overlap with Illuminate\Cache.
- Can I install tempest/kv-store in a Laravel app with Composer?
- Composer-wise it is installable. It is MIT licensed and published as a read-only sub-split precisely so it can be installed standalone outside the Tempest monolith. The real risk is the dependency graph: Tempest components commonly pull tempest/support, tempest/core, and PSR-11 container contracts, so a Laravel 10 or 11 app on PHP 8.2 or 8.3 will likely hit constraint conflicts. Prove the graph resolves in a throwaway branch before planning any integration work.
- What PHP version does tempest/kv-store require?
- The assessment flags recent Tempest releases as tracking PHP 8.4 and above, which is stricter than many Laravel 10 and 11 installs running 8.2 or 8.3. Check the composer.json of the exact tagged release rather than trusting the README, because the floor moves with Tempest's release cadence. If you are pinned below that floor, the package is not a candidate without a PHP upgrade.
- Does tempest/kv-store require the Tempest framework or container to work?
- This is the key unresolved question and it determines whether the package is a library or an ecosystem commitment. The component is described as a key-value abstraction with pluggable drivers, but driver resolution in Tempest typically goes through its container and discovery conventions. Verify whether you can construct the store with a driver instance standalone, or whether it expects the Tempest container.
- Which storage drivers ship with tempest/kv-store?
- The available material describes pluggable drivers with file-backed and in-memory stores, plus the Redis and array variants typical of this pattern. Confirm the actual in-tree driver list in the release you install. If you need Redis semantics, check whether that driver is bundled or whether you must write your own adapter.
- Does tempest/kv-store implement PSR-16 simple cache?
- Unclear from the available material, and the assessment explicitly lists it as an open question. The contract appears to be Tempest-proprietary rather than a PSR-16 adapter. If PSR-16 interoperability matters to your codebase, use symfony/cache or Illuminate\Cache, both of which are mature and fully documented.
- How does tempest/kv-store compare to Laravel's Cache facade and Illuminate\Cache?
- Laravel already ships file, array, database, Redis, Memcached, and DynamoDB stores with TTL, tags, locks, and atomic increments. tempest/kv-store offers a simple, consistent key-value API but no comparable feature set and no ecosystem evidence of production use. For a Laravel application the correct answer is almost always Illuminate\Cache. tempest/kv-store only becomes rational if you are explicitly evaluating Tempest itself.
- Does tempest/kv-store support TTL, atomic increments, and cross-process locking?
- The overview promises storing, retrieving, and managing persisted values, but does not document TTL precision, atomic increment and decrement, compare-and-swap, or cross-process locking. The assessment lists all of those as questions to resolve before any commitment. Do not assume Laravel Cache-grade semantics, and read the driver source carefully, especially the file driver's fsync behaviour, lock contention, and crash recovery model.
- Is tempest/kv-store maintained and production ready?
- It is MIT licensed and published as a read-only sub-split, which is a positive feasibility signal. Adoption evidence is essentially zero, with no stars, no dependents, and no peer precedent in production. Issues and pull requests route to the tempest/framework monorepo, so you cannot fork and patch cleanly inside your own review process, and a small core team means key-person and roadmap risk are disproportionate for a key-value store.
- What should I use instead of tempest/kv-store in a Laravel application?
- Use Illuminate\Cache if you are inside Laravel, or symfony/cache and a PSR-16 implementation if you want a framework-agnostic contract. Both have documented Redis and file drivers, stable semantics, and broad production use. tempest/kv-store is only rational as one leaf of a much larger Tempest framework spike, not as a drop-in utility for a Laravel estate.