Roadrunner Kv Laravel Package

Product Decisions This Supports

• Enables low-latency caching and state sharing between workers without external dependencies, reducing infrastructure costs and complexity.
• Supports roadmap decisions to avoid building custom KV layers by leveraging RoadRunner’s native plugin, accelerating delivery of features that rely on transient data.
• Ideal for use cases like session caching, temporary computation results, or lightweight state synchronization where full database overhead is unnecessary.
• Drives "build vs buy" decisions by providing a maintainable, MIT-licensed solution instead of custom code or additional services like Redis for simple key-value scenarios.
• With v4.5.0, RoadRunner v3 support keeps the caching layer aligned with the current runtime roadmap, avoiding a fork or a bespoke compatibility shim during platform upgrades.

When to Consider This Package

• Adopt when using RoadRunner as the application server (now v3-compatible via v4.5.0) and needing fast, ephemeral storage for small data (e.g., <1MB keys) with basic operations (get/set/delete).
• Suitable for high-performance PHP workers where data persistence is tied to the worker lifecycle (e.g., caching API responses between requests).
• Plan the dependency migration: v4.5.0 renames the package to roadrunner/kv, so composer.json references, imports, and any internal documentation must be updated. Treat this as a breaking change in upgrade planning and pin accordingly.
• Avoid if data requires persistence beyond worker restarts, complex queries, transactions, or large-scale storage—opt for Redis/PostgreSQL instead.
• Not applicable for non-RoadRunner environments (e.g., PHP-FPM, Swoole) or when needing advanced features like pub/sub or cross-service messaging.

How to Pitch It (Stakeholders)

For executives: this release keeps our caching layer current with RoadRunner v3 and renames the package to roadrunner/kv, which is a low-effort dependency migration we should schedule in a maintenance window. No new infrastructure, licensing cost, or vendor commitment is introduced—it protects the "avoid Redis for simple key-value" cost decision already on the roadmap. For engineering: update the Composer requirement to roadrunner/kv at ^4.5, verify the RoadRunner v3 runtime, and re-run the worker cache integration tests; the API surface for get/set/delete is unchanged, so feature code should not need modification.