Weave Code
Execution Cache Bundle Laravel Package
stadline/execution-cache-bundle
Symfony bundle for caching the results of expensive executions so repeated calls reuse stored output instead of recomputing it. Configure cache adapters and lifetimes to speed up heavy service or method calls.
Provides execution cache for Symfony controllers.
Frequently asked questions about Execution Cache Bundle
- What does stadline/execution-cache-bundle actually do?
- It is a Symfony bundle that stores the results of expensive controller executions so repeated calls reuse the cached output instead of recomputing it. You configure a cache adapter and a lifetime, and the bundle skips the heavy work on subsequent calls. The available 0.2.0 notes list only three additions: bundle configuration, an annotation, and documentation. No source review, dependency manifest, or test coverage data was provided, so treat performance and compatibility claims as unverified until you spike it.
- How do I install stadline/execution-cache-bundle with Composer?
- Install it with Composer require stadline/execution-cache-bundle, then confirm what constraints resolve on your platform. Because it is a Symfony bundle rather than a Laravel package, you register it in config/bundles.php for the environments where you want it enabled instead of relying on Laravel package auto-discovery. After registration, import or publish the bundle configuration so the cache adapter and lifetimes are set. No composer.json was reviewed, so verify the PHP and Symfony ranges before committing.
- Is this a Laravel package or a Symfony bundle?
- It is a Symfony bundle, which the package name and the controller-oriented description both make clear. There is no evidence of a Laravel service provider, facade, or Artisan commands, and the configuration idiom described is Symfony-style bundle configuration rather than mergeConfigFrom plus vendor:publish. Laravel developers should treat it as an architectural reference or a porting candidate, not a drop-in dependency. If you need execution caching in Laravel, the framework's own cache and middleware layers are the more idiomatic route.
- Does the bundle use PHP 8 attributes or docblock annotations?
- The release notes only say an annotation was added, so the mechanism is unconfirmed. On modern PHP the likely implementation is PHP 8 attributes, but Doctrine-style docblock parsing cannot be ruled out and would be a red flag on current runtimes. Attributes imply reflection or class-file scanning, which brings boot-time cost on every request and cache invalidation problems when classes move or are added. Read the source before adopting and check specifically whether scan results are cached and how that cache is cleared.
- How do I configure the cache adapter and cache lifetimes?
- Configuration arrives in 0.2.0 as bundle configuration, which in Symfony means a config tree under the bundle alias in config/packages. You point it at a cache pool or adapter and set the lifetime applied to cached executions. The exact keys are not visible in the available material, so read the bundle's extension class and the shipped documentation. Because the config surface was introduced at 0.2.0, expect keys to churn before 1.0, and avoid spreading them across many config files.
- Which PHP and Symfony versions does this package support?
- The available material contains no dependency manifest, so supported PHP and Symfony ranges are unknown. Check Packagist metadata or run a Composer require in a throwaway branch and inspect what constraints resolve on your platform. If you are on a current Symfony LTS, verify compatibility explicitly before planning adoption. Treat any assumed version matrix as a hypothesis rather than a documented guarantee.
- Is version 0.2.0 stable enough to run in production?
- It is pre-1.0, which under semver means a minor bump such as 0.3.0 may contain breaking changes. The 0.2.0 release is additive rather than breaking, but additive features are not evidence of API stability. For production, pin an exact version, wrap usage behind your own service or decorator, and budget time to absorb upgrades. Confirm whether the maintainers publish breaking changes in a changelog before you commit.
- How do I clear or invalidate cached executions?
- Cached output lives in whichever cache adapter you configure, so the standard Symfony cache pool commands apply for clearing entries. Whether the bundle ships its own console command for purging entries is not confirmed in the available notes, so check for one before assuming. Plan a deploy hook that clears the relevant pool, and verify what happens when the annotation metadata on a controller changes. Manual invalidation on a per-execution basis may require key naming you control.
- How do I test code that relies on execution caching?
- Use a null or array cache adapter in the test environment so each test starts cold and cached output cannot leak between cases. Because caching sits around controller execution, functional tests should assert response bodies rather than internal call counts. Include one test for the cold path and one that hits the same execution twice to prove the cache is used. Keep cache pools isolated per test kernel to avoid flaky, order-dependent failures.
- What are the alternatives to this bundle?
- In Laravel, the same effect is usually achieved with Cache::remember around the expensive call or with response caching middleware, both more idiomatic for Laravel developers. In Symfony, HttpCache and the standard cache contracts cover similar ground at the HTTP layer. This bundle's narrower value is declarative caching of specific controller executions through configuration and an annotation. Choose it only if that declarative shape saves more than the cost of adopting a pre-1.0 dependency.
Weaver
How can I help you explore Laravel packages today?