Product Decisions This Supports

Enables rapid implementation of real-time features (e.g., live notifications, collaborative tools) without custom HTTP client code
Supports roadmap goals for scalable, low-latency backend infrastructure by leveraging Centrifugo's pub/sub architecture
Build vs. buy: Avoids reinventing the wheel for Centrifugo integration—ideal for teams using RoadRunner where manual implementation would add maintenance overhead
Critical use cases: High-throughput scenarios like real-time dashboards, multiplayer gaming backends, or live event streaming where the PHP backend must push updates to clients
Platform currency (new in 2.5.0): RoadRunner v3 support keeps the real-time layer aligned with our runtime upgrade roadmap—removing a potential blocker for adopting the newest RoadRunner release across services
Migration planning input: the 2.5.0 rename to roadrunner/centrifugo is a dependency-naming change that affects composer.json and any internal references; budget a small, scheduled upgrade ticket rather than an unplanned mid-sprint change

When to Consider This Package

Adopt when:
- Your stack uses RoadRunner (v3 supported as of 2.5.0) and Centrifugo as the real-time server
- You need a lightweight, framework-agnostic PHP client for Centrifugo's HTTP API
- Your team prioritizes simplicity over advanced features (e.g., no need for client-side SDKs or enterprise support)
Look elsewhere when:
- Using non-PHP/RoadRunner stacks (e.g., Node.js, Python) or alternative real-time services (e.g., Pusher, Firebase)
- You require client-side SDKs or advanced Centrifugo features (e.g., presence, history) not covered by this bridge
- Project scale is small and real-time needs are minimal (e.g., basic WebSocket fallbacks may suffice)
Version-fit checks before upgrading to 2.5.0:
- Confirm target RoadRunner version—2.5.0 adds RoadRunner v3 support; verify whether RoadRunner v2 remains supported before pinning, and pin explicitly if you are not yet on v3
- Update the Composer package name to roadrunner/centrifugo and audit lockfiles, CI caches, internal docs, and any use statements or service-provider references for namespace drift
- Treat as a controlled upgrade: this is a major-adjacent release (rename + runtime version support), so validate in staging before rollout

Executives: "This package lets us deliver real-time user experiences—like live notifications and collaborative tools—with minimal engineering effort. The new 2.5.0 release keeps us current with RoadRunner v3, so our real-time layer won't block our platform upgrade plans. Cost remains a zero-licensed, low-effort integration, and the only added work is a small, planned dependency rename we can schedule alongside existing maintenance."
Engineering: "2.5.0 renames the package to roadrunner/centrifugo and adds RoadRunner v3 support. The API for Centrifugo interactions is unchanged in spirit—still a clean, dependency-light client that removes manual HTTP glue—but the upgrade touches composer.json, lockfiles, and any namespace or provider references, so we should treat it as a deliberate migration task with a staging validation pass. Teams still on RoadRunner v2 should confirm continued support before upgrading, and pin the version accordingly."