- What is amelia/rememberable used for in Laravel?
- amelia/rememberable is a Laravel package that adds rememberable caching to Eloquent models so query results can be stored and reused. It is intended as a lightweight helper for read-heavy application areas that make repeated database calls. The package is Laravel 5-era and best treated as a reference implementation rather than a modern production dependency.
- Does amelia/rememberable support Laravel 8, 9, 10, or 11?
- No, it should not be assumed to support modern Laravel versions. The package targets Laravel 5.2+ and was last released in 2016, so it likely depends on older Eloquent and query-builder internals. Using it on Laravel 6+ should be treated as a porting project, not a normal Composer install.
- How do I install amelia/rememberable in a Laravel application?
- Installation is only realistic in a legacy Laravel 5 application that matches the package's PHP and Laravel constraints. Vendor the package, pin the exact commit, and register any required service provider manually if your Laravel version does not support package discovery. Do not introduce it into a modern Laravel app without a compatibility audit and fork.
- Which cache drivers work with amelia/rememberable?
- The package depends on Laravel's cache layer, so practical driver choice is Redis, Memcached, or another configured Laravel cache store. Cache effectiveness and safety depend heavily on backend choice, key design, and invalidation behavior. Validate the selected driver in a non-production proof of concept before relying on it.
- How are cache keys generated and invalidated when models change?
- Cache-key behavior is not well documented and should be treated as opaque until audited in your fork or proof of concept. Invalidation gaps are a major risk, especially around model events, bulk updates, transactions, global scopes, soft deletes, and relationship queries. Define explicit invalidation rules and add tests for cache hits, misses, and stale-data scenarios.
- Is amelia/rememberable safe for production use?
- Treat it as high risk for production because it is effectively unmaintained, last released in 2016, and has little community validation. Risks include stale query results after writes, cache-key collisions, missed invalidation, and compatibility breaks during Laravel or PHP upgrades. If used at all, roll it out behind a feature flag with monitoring and rollback criteria.
- How should I test query caching with amelia/rememberable?
- Add integration tests around cache hits and misses, write-driven invalidation, bulk updates, and relationship queries. Test against the exact Laravel minor version, PHP version, and cache backend you plan to use. Also test failure modes such as cache outages, stale data after writes, and multi-tenant isolation if applicable.
- Does amelia/rememberable work with multi-tenancy, transactions, and soft deletes?
- Support for multi-tenancy, transactions, soft deletes, and complex Eloquent features is undocumented and should not be assumed. These areas are common sources of cache-key and invalidation defects in query-caching packages. Audit them explicitly in a fork or proof of concept before using the package in any shared or tenant-aware application.
- What are alternatives to amelia/rememberable for Laravel query caching?
- For most modern Laravel applications, native Cache::remember or a maintained model-cache package is a better fit. You can also use amelia/rememberable only as a design reference for building an internal query-caching utility. Avoid adopting it directly when a maintained alternative or native caching meets the requirement.
- Is amelia/rememberable still maintained, and should I fork it?
- There is no evidence of active maintenance, and the last release was in 2016 with very few dependents or stars. If a legacy Laravel 5 application truly needs it, budget for a named owner, pinned commits, runbooks, and periodic compatibility testing. Otherwise, reject it or sponsor a short spike to see whether its caching model can inform an internal implementation.