Weave Code
Laravel Valkey Glide Laravel Package
sinemacula/laravel-valkey-glide
A Laravel integration for Valkey GLIDE, the official client library for the Valkey in-memory store. It lets Laravel applications use Valkey as a fast, Redis-compatible backend for caching, sessions and queues through a native connection driver and straightforward configuration.
A Laravel integration for Valkey Glide, the official high-performance client for Valkey. It brings Glide’s native client into Laravel’s cache and Redis-compatible workflows, letting you use Valkey as a fast, reliable backing store without adapting your application code.
- Config-driven Valkey Glide connections
- Laravel cache store integration
- Support for TLS and authentication
- Compatible with Valkey’s Redis-style commands
- Lightweight setup for local and production environments
Frequently asked questions about Laravel Valkey Glide
- What is sinemacula/laravel-valkey-glide used for?
- It provides a Laravel Redis driver and adapter for Valkey GLIDE so Laravel applications can connect to Valkey through Glide's Rust-based client. It is an infrastructure-swap package that keeps usage inside Laravel's existing cache and key-value driver abstractions.
- How do I install sinemacula/laravel-valkey-glide with Composer?
- Install it as a Composer dependency in your Laravel application, typically with composer require sinemacula/laravel-valkey-glide. Then follow the README to register or select the package's driver in your Laravel cache configuration.
- How do I configure the Valkey GLIDE driver in Laravel's config/cache.php?
- Add or select a cache store in config/cache.php that uses the driver registered by this package, then point it at your Valkey endpoint and credentials. The package is designed to fit Laravel's familiar cache store configuration rather than requiring application code changes. Check the README for the exact driver name and supported store options.
- Does laravel-valkey-glide support Laravel 13, Laravel 12, and Laravel 11?
- Version 1.1.0 added Laravel 13 support as a minor release with no declared breaking changes or configuration changes. The release note implies support is additive rather than a replacement, but the exact illuminate constraint is not specified in the provided context. Verify the Composer constraint directly before committing to a Laravel version matrix.
- Can I use this Valkey driver alongside phpredis or predis in the same Laravel app?
- Yes, because the driver sits behind Laravel's cache contracts, you can run it alongside an existing phpredis or predis store. That allows per-application or per-environment switching and a canary rollout without forking application code. Applications that use the Cache facade rather than raw clients should see the smallest blast radius.
- What native dependencies does Valkey GLIDE add to a Laravel deployment?
- GLIDE clients ship a native component, so you must confirm which PHP extension, FFI, or shared-library mechanism the pinned GLIDE version requires. Check that your base images, including glibc versus musl or Alpine, and your CI runners are supported. Also confirm that the required PHP and Laravel versions match your platform baseline.
- Is laravel-valkey-glide production-ready?
- The package is described as providing reliable, production-grade Valkey connectivity, but the dominant adoption risk is single-maintainer concentration rather than code quality. Native GLIDE dependencies and possible behavioral differences from phpredis or predis also need production validation. Treat it as a thin adapter, canary it, and test locks, tags, and TTL behavior before broad rollout.
- How should I test a Laravel app using the Valkey GLIDE cache driver?
- Because the driver sits behind Laravel's cache contracts, test through the Cache facade rather than calling Glide directly. Run integration tests against a real Valkey instance and include TTL, lock, and tag invalidation cases. Also verify that your CI runner and deployment base image support the native GLIDE component.
- Are cache locks, tags, and TTLs compatible with Laravel's Redis driver behavior?
- Cache semantics such as serialization, TTL handling, tag support, locks, and atomic operations may not be byte-identical to phpredis or predis. Silent differences in Cache::lock behavior or tag invalidation are the classic failure mode for cache drivers. Test these cases explicitly before relying on the driver in production.
- What are the alternatives to laravel-valkey-glide, and is it maintained?
- The main alternatives are Laravel's existing phpredis or predis Redis driver, or using the Valkey GLIDE client directly outside Laravel's cache abstraction. Maintenance is the key trade-off: v1.1.0 added Laravel 13 support in a minor release, which is a good sign, but this is a single-maintainer package. Because the adapter is small, you could vendor or reimplement the cache store if it stalls.
Weaver
How can I help you explore Laravel packages today?