Weave Code
Redis Schema Bundle Laravel Package
macpaw/redis-schema-bundle
Symfony bundle from MacPaw that adds a schema layer for Redis, letting you declare typed key structures and entities with serialization and lifecycle management instead of scattering raw Redis commands and key names across your application.
A Symfony bundle to add schema prefixes for redis keys
Frequently asked questions about Redis Schema Bundle
- Can I use macpaw/redis-schema-bundle in a Laravel application?
- It is a Symfony bundle, not a Laravel package. Laravel has no Bundle extension point, so the bundle's DependencyInjection extension, compiler passes, and tagged-service wiring will not be picked up. Adopting it means running a second Symfony container, forking the wiring as a ServiceProvider, or vendoring only the schema and repository classes. The last option has the best cost/benefit for Laravel teams.
- Does this package support Laravel 10 or Laravel 11?
- There is no documented Laravel support. The package targets Symfony's bundle contract, and Laravel's service providers and config repository are not compatible with that contract. Treat any Laravel version claim as unverified until a fork is explicitly tested against that framework version. Also check whether the bundle's Symfony component constraints conflict with Laravel's pinned symfony packages.
- What does a Redis schema bundle actually do?
- It adds a declarative schema layer over Redis, letting you define typed key structures and entities with serialization and lifecycle management. Instead of scattering raw Redis commands and key-name strings across the codebase, you declare the schema once and access data through typed repositories. The conceptual layer is portable, but most of the bundle's value in this package is tied to Symfony DI wiring.
- How do I install macpaw/redis-schema-bundle with Composer?
- You can require it with Composer, but in a Laravel app the bundle will not register itself. Installation alone does not produce a working integration because Laravel does not read Symfony bundle manifests or run bundle extensions. For Laravel, plan to extract or fork the schema code rather than depend on the bundle directly.
- Is macpaw/redis-schema-bundle maintained and safe for production?
- The public signals are weak: roughly one star, zero dependents, and no visible production usage. There is no stated deprecation policy, support commitment, or roadmap, and there are no production bug reports, which is not the same as no production bugs. The anomalous future release date also suggests release automation may be absent, so verify maintenance status directly before relying on it.
- What is the best alternative to redis-schema-bundle for Laravel?
- For Laravel, the pragmatic alternative is to treat this repository as a reference implementation and build a small Laravel-native package. Bind schema repositories as singletons around phpredis or Predis and keep key-naming conventions in config. That avoids maintaining two dependency injection paradigms and keeps Laravel's Redis configuration authoritative.
- How do I integrate this Symfony bundle into Laravel if I must use it?
- Fork it, publish it under an internal namespace, and add a ServiceProvider that builds the schema registry from a config file and binds the repository interfaces. You will also need to register the tagged-service equivalents manually, because Laravel will not process Symfony tags. Budget for the fork to diverge permanently since the wiring layer is exactly what you replaced.
- Is the bundle compatible with Redis Cluster, Sentinel, and different Redis clients?
- The available context does not answer this, and it should be treated as a key due-diligence question for maintainers. Ask whether key generation emits Redis Cluster hash tags, whether multi-key operations are cluster-safe, and which clients such as ext-redis, Predis, or Relay are supported. Also confirm Sentinel failover behavior and documented failure semantics under eviction before committing.
- Is the key schema and serialization format stable across minor versions?
- That is not documented in the excerpt, and it is the main lock-in risk. If the schema layer owns key naming and value encoding, migrating off it later becomes a live-data migration rather than a refactor. Ask for a versioned key schema and any migration or backfill tooling before adopting it.
- Which Symfony and PHP versions does redis-schema-bundle support, and is there a CI matrix?
- The provided material does not include a supported Symfony or PHP version range. Ask the maintainers which versions are supported and whether a CI matrix proves compatibility. This matters especially in Laravel because Laravel pins its own symfony component versions, and a differing major constraint on packages like symfony/config or symfony/dependency-injection can block installation or cause runtime conflicts.
Weaver
How can I help you explore Laravel packages today?