Weave Code
Staccache Bundle Laravel Package
phillarmonic/staccache-bundle
phillarmonic/staccache-bundle is a PHP caching bundle that helps wire stacked cache layers into your application, with straightforward configuration and service integration for Symfony projects. A lightweight option for organizing cache behavior in existing apps.
A Symfony bundle for entity caching with locking support
Frequently asked questions about Staccache Bundle
- What is phillarmonic/staccache-bundle and what problem does it solve?
- phillarmonic/staccache-bundle is a Symfony bundle for stacked, multi-layer caching. It lets you combine fast in-memory stores such as array or APCu with persistent backends such as Redis, so reads hit the cheapest layer first. It integrates with Symfony's Cache Contracts while preserving existing CacheInterface usage. The main benefit is transparent promotion and fallback between cache layers.
- Does phillarmonic/staccache-bundle work with Laravel?
- The package is published as a Symfony bundle and plugs into Symfony's cache contracts, not Laravel's cache system. The available context does not confirm Laravel auto-discovery, service-provider behavior, config publishing, or Laravel version support. Laravel teams should treat it as unproven for Laravel and run a compatibility spike before adoption. Confirm PHP and framework constraints with a locked Composer test.
- How do I install phillarmonic/staccache-bundle with Composer?
- Install it as a Composer dependency in a disposable branch and verify the resolved dependency tree. Because v1.0.0 is the initial release, check the exact package metadata, license, README, and changelog before merging. Run the host application's test suite after installation. For Symfony projects, confirm bundle registration and configuration loading match your app's conventions.
- How do I configure stacked cache layers like array, APCu, and Redis?
- The bundle is described as configurable through config/packages YAML with sane defaults for multiple cache layers. You can combine stores such as array, APCu, and Redis in one stack so reads check the fastest layer first. Exact option names and adapter requirements should be taken from the package README and validated in a sandbox. Test cache isolation, TTL behavior, and backfill behavior for each adapter you enable.
- Does staccache-bundle support Symfony Cache Contracts and PSR-6/PSR-16?
- Yes, the package overview states that it works with Symfony's Cache Contracts and PSR-6/PSR-16. That means existing CacheInterface usage should keep working while the bundle adds stacked-layer behavior underneath. You should nevertheless verify the exact interfaces and adapter implementations your application relies on. Confirm behavior for cache misses, key normalization, TTLs, and serialization in a technical spike.
- Which PHP and Symfony versions are supported by phillarmonic/staccache-bundle?
- The provided release information does not include a documented PHP or Symfony compatibility matrix. v1.0.0 is the first release, so compatibility must be verified against your exact PHP, Symfony, and Composer versions. Require a documented compatibility statement before production adoption. Use a locked Composer resolution in a disposable branch to detect dependency conflicts early.
- How does read-through promotion and fallback between cache layers work?
- The bundle describes automatic read-through behavior: a cache miss cascades to the next layer and then backfills the faster layer. That gives you transparent promotion and fallback without changing your existing CacheInterface calls. The exact backfill policy, TTL handling, and eviction behavior should be confirmed from the package documentation and tests. Validate that stale or partial data cannot be promoted incorrectly in your use case.
- Is there a test suite or CI matrix for production use?
- The available context does not confirm test coverage, CI matrix, static analysis, or a security policy for v1.0.0. First-release packages carry high initial uncertainty, so production adoption should require inspection of the repository, changelog, and test suite. Run your own integration tests in a sandbox before relying on the bundle. Define acceptance criteria and a rollback path before broader rollout.
- What are alternatives to staccache-bundle for multi-layer caching?
- Alternatives depend on your framework: Symfony's native cache component and chain adapter, Laravel's cache repositories, or custom layered cache decorators can provide similar behavior. Evaluate them against the same criteria: interface compatibility, backfill semantics, supported adapters, and operational visibility. For Laravel applications, a native Laravel cache abstraction is usually safer until staccache-bundle's Laravel support is confirmed. Compare maintenance, test coverage, and license before choosing.
- How do I roll back or uninstall phillarmonic/staccache-bundle safely?
- Because this is the initial release, there is no prior package version migration path to follow. Adopt it as an additive pilot behind an abstraction or feature flag, and keep the existing cache path available until parity is proven. To roll back, remove the Composer dependency, revert bundle registration and configuration, and rerun the host application's test suite. Confirm whether the package publishes config, migrations, routes, middleware, events, or jobs before uninstalling.
Weaver
How can I help you explore Laravel packages today?