- What is swayok/alternative-laravel-cache?
- swayok/alternative-laravel-cache is a drop-in cache package for Laravel that adds proper tagging behavior to file and database cache stores. It lets you use Laravel's familiar Cache::tags() API without requiring Redis or Memcached. It is intended for applications that want tagged cache invalidation while keeping a simple Laravel cache setup.
- How do I install swayok/alternative-laravel-cache with Composer?
- Install it with Composer using composer require swayok/alternative-laravel-cache. Then configure the package's cache store according to its README and use the normal Laravel cache API. The 6.3.3 release is described as a patch upgrade with no new migrations or public API changes.
- Which Laravel versions does this package support?
- Release 6.3.3 specifically removes usage of the Laravel 13-only CanFlushLocks interface to restore compatibility with Laravel 12 and earlier. The package is intended to remain usable across supported Laravel versions, but you should confirm the declared Laravel and PHP support matrix in its composer.json and release notes. Test lock-related behavior if your application runs on Laravel 13 or later.
- Can I use Cache::tags() with Laravel file and database cache stores?
- Yes. The package is described as bringing tag support to file and database cache stores so Cache::tags() works with those drivers. That makes it useful when your application needs tag-based invalidation but you do not want to run Redis or Memcached. Check the package documentation for the exact store configuration.
- Do I need Redis or Memcached to use tagged caching with this package?
- No, the main purpose of this package is to provide tagged caching without requiring Redis or Memcached. It targets Laravel file and database cache stores, which normally lack full tag support. If you already use Redis or Memcached, Laravel's native tagged cache support may be sufficient.
- How is swayok/alternative-laravel-cache configured in a Laravel app?
- It is designed as a drop-in alternative cache for Laravel, so setup is handled through Laravel's cache configuration and the package's documented store options. The 6.3.3 release notes do not indicate new configuration, migrations, or deprecations. Follow the README for the exact driver and store configuration.
- What changed in version 6.3.3 of this package?
- Version 6.3.3 removes usage of CanFlushLocks, an interface available only since Laravel 13, to restore compatibility with Laravel 12 and earlier. It is a compatibility-oriented patch rather than an architectural change. No breaking API changes, new configuration, migrations, or deprecations are indicated in the release notes.
- Is upgrading to 6.3.3 safe for production Laravel applications?
- The technical risk is described as low but not zero. The main concern is a possible behavioral regression in lock flushing or cache-lock cleanup on Laravel 13+ after CanFlushLocks usage was removed. Upgrade in development and staging first, and specifically exercise lock-related workflows before broad production rollout.
- How should I test the upgrade to this alternative Laravel cache package?
- Update the Composer constraint, refresh dependencies, and run your application test suite. Then test lock-related workflows, cache invalidation, and representative cache usage on each Laravel version you support. A canary or limited production rollout is prudent if locks are used in queues, scheduled jobs, or other concurrent workflows.
- Is this package maintained, and what are the alternatives for tagged Laravel caching?
- The package appears maintained through compatibility-oriented patches such as 6.3.3, but you should check GitHub and Packagist for current release cadence and support status. Alternatives include Laravel's native Redis or Memcached tagged cache stores, or building a custom cache store with your own tag handling. This package is the better fit when you want tag semantics with file or database stores and no Redis or Memcached dependency.