Weave Code
Simple Cache Bundle Laravel Package
kitpages/simple-cache-bundle
A lightweight Symfony bundle that provides a simple caching service for storing and retrieving values through an easy API. It helps reduce repeated work and speed up small applications without complex configuration.
Very simple cache system for symfony2. The cache data are saved in one table in database.
Frequently asked questions about Simple Cache Bundle
- Does kitpages/simple-cache-bundle work with Laravel?
- No. KitpagesSimpleCacheBundle is a Symfony bundle, and its entire integration value comes from registering a cache service into Symfony's dependency injection container through the bundle and kernel lifecycle. Laravel has no bundle lifecycle, so that mechanism is inert in a Laravel application. What is left underneath is a thin key/value wrapper you would have to instantiate and configure by hand, which is a framework mismatch rather than an architecture fit.
- Can I install kitpages/simple-cache-bundle with Composer in a Laravel app?
- There is no clean composer require path. A Symfony 2-era bundle typically pins symfony/* constraints that conflict with the illuminate/* tree, and PHP support is almost certainly pre-8.0. You would either force a pinned legacy dependency set, which is unacceptable, or bypass the bundle and reimplement its wrapper behavior, at which point the package contributes nothing.
- Which PHP and Symfony versions does this bundle support?
- The bundle targets the Symfony 2 era, so expect pre-8.0 PHP constraints and outdated symfony/* requirements. There is no named upstream maintainer and no release cadence, so no compatibility fix is coming. Any dependency resolution you force to make it install becomes yours to carry indefinitely.
- What cache backends does KitpagesSimpleCacheBundle support?
- It ships a pluggable backend model with adapters for filesystem and APC, plus room for other adapters behind the same service API. Storage is wrapped behind a simple service so get, set and remove calls stay identical regardless of backend. For most Laravel use cases, the native store abstraction already covers file, Redis, Memcached and APCu without a third-party wrapper.
- Does this bundle support cache expiration and TTL?
- Yes. Stored entries support cache expiration through a TTL, which is the main functional feature the bundle offers. That is also table stakes for Laravel's cache layer, where put and remember accept a TTL directly, so it is not a differentiator.
- What is the Laravel equivalent of this Symfony cache bundle?
- Illuminate\Support\Facades\Cache, bound through a service provider or resolved as a named store. It gives you multiple stores, tagged caching on Redis and Memcached, atomic locks, and PSR-16/PSR-6 interoperability. The bundle's mental model of a simple cache service registered with the framework maps almost one-to-one onto a named Laravel cache store.
- Is kitpages/simple-cache-bundle maintained and safe for production?
- The signals are uniformly negative: around 5 stars, 0 dependents, an aggregate score near 0.115, no named maintainer and no release cadence. The one clean signal is the MIT license. Caching is a high-blast-radius domain where stale or misconfigured entries become silent data-integrity bugs, so taking that risk on unmaintained code is a poor trade.
- How do I migrate from this Symfony cache service to Laravel's cache?
- Extract the behavior, not the package. Inventory the cache keyspace, TTL policy and serialization format, then reimplement behind a stable CacheRepository interface backed by Cache::store('redis'). Keep the interface signature identical so call sites do not change, and dual-read behind a feature flag during cutover. Do not vendor the bundle, because the fork liability exceeds any salvage value.
- How do I test a caching layer built on Laravel's cache instead of this bundle?
- Bind your CacheRepository interface to a fake or an in-memory array store in the test container so unit tests never touch a real backend. Laravel's Cache::fake() also lets you assert that keys were written, read and forgotten. That level of testability is straightforward with a native store and far harder to achieve when the caching logic is locked inside a foreign bundle.
- Is there a simpler alternative to this bundle for a lightweight cache abstraction?
- Yes, use Laravel's cache facade directly. A native cache store bound in a service provider covers this entire surface in hours, versus days of shim work for a 5-star, zero-dependent library. The underlying problem of teams wanting a dead-simple cache abstraction is real, but the native abstraction already solves it.
Weaver
How can I help you explore Laravel packages today?