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 feature delivery for transient data needs.
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.

When to Consider This Package

Adopt when using RoadRunner as the application server 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 worker lifecycle (e.g., caching API responses between requests).
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