Product Decisions This Supports

Enables high-performance internal APIs and microservices communication, reducing latency and increasing throughput compared to REST/HTTP.
Supports roadmap shifts toward service-oriented architecture by providing a robust RPC framework without building custom solutions.
Build vs buy: Leverages existing RoadRunner infrastructure to avoid reinventing gRPC tooling, saving development time and maintenance costs.
Critical for use cases requiring real-time streaming (e.g., live data feeds), high-throughput transactional systems (e.g., payment processing), or strict contract-driven service interactions via Protocol Buffers.

When to Consider This Package

Adopt when using RoadRunner as the PHP application server and needing low-latency, high-concurrency RPC for microservices or internal APIs.
When strict service contracts via Protocol Buffers are required for type safety, versioning, and cross-language compatibility.
Avoid if the project uses non-RoadRunner PHP environments (e.g., traditional PHP-FPM with Apache/Nginx), is small-scale with simple API needs, or if REST/JSON is sufficient for communication.
Not ideal for teams unfamiliar with gRPC/Protobuf without dedicated upskilling or if the team lacks experience with persistent worker models.

Executives: "This package slashes infrastructure costs by handling 5–10x more requests per server than REST-based systems, while ensuring critical internal workflows run faster and more reliably. It’s a proven, open-source solution that integrates seamlessly with our existing RoadRunner stack—no custom development needed."
Engineering: "It delivers battle-tested gRPC support for RoadRunner with automatic Protobuf code generation, ensuring type-safe, efficient communication. Streaming RPCs and persistent workers handle high concurrency with minimal overhead, and the MIT license keeps us flexible. Integration is straightforward with our current RoadRunner setup, reducing onboarding friction."