gRPC
A high-performance open-source Remote Procedure Call (RPC) framework developed by Google, built on HTTP/2 and Protocol Buffers. Donated to the CNCF for stewardship, it is widely used for communication in cloud-native and microservices architectures.
Core Facts
Timeline (last 90 days)
The API world suffers from fragmentation: different styles such as REST, GraphQL, and gRPC, and each vendor's naming conventions, authentication methods, and error code definitions all differ, which is extremely inefficient for AI models.
gRPC uses Protocol Buffers serialization on top of HTTP/2, which can reduce payload size by 30–50% compared to JSON and supports server-side streaming.
Capabilities that need to be dynamically discovered by AI or triggered by natural-language-described intent are suitable for exposure via MCP; fixed machine-to-machine calls between systems and scenarios with strict requirements on latency or throughput should go directly through traditional APIs such as REST or gRPC.
Streaming voice typically relies on bidirectional streaming protocols based on WebSocket or gRPC, or HTTP streaming based on chunked transfer encoding.
REST remains the dominant API style, GraphQL is increasingly popular in scenarios requiring flexible queries, and gRPC is widely adopted in microservice communication for its high performance and strongly typed contracts.
The gRPC framework uses protobuf as its default interface description language (IDL)
The proto used by vLLM is typically based on Protocol Buffers (protobuf) and is commonly used in conjunction with the gRPC framework.
RPC (Remote Procedure Call) is action-centric, with interfaces directly describing callable functions; common implementations include Google's gRPC (based on Protocol Buffers and HTTP/2) and JSON-RPC.
The same FLARE training code can communicate via local networking in Docker Compose, discover each other via Service in K8s Pods, and exchange model updates via gRPC persistent connections between Slurm job nodes.
gRPC uses Protocol Buffers (.proto files) as its interface description language.
6 more timeline events
All Facts (20)
gRPC is a cross-language RPC framework open-sourced by Google, based on the HTTP/2 protocol and Protocol Buffers serialization.
80%UnverifiedA2A协议的传输层使用JSON-RPC 2.0走HTTPS，长任务用Server-Sent Events做流式更新或Webhook做异步通知，版本0.3还加了gRPC支持
90%Unverifiedrunn支持HTTP/gRPC等协议的接口测试
90%UnverifiedGoogle的API遵循gRPC状态码规范
80%UnverifiedgRPC uses Protocol Buffers by default as its interface definition language and message serialization format.
60%UnverifiedThe API world suffers from fragmentation: different styles such as REST, GraphQL, and gRPC, and each vendor's naming conventions, authentication methods, and error code definitions all differ, which is extremely inefficient for AI models.
50%UnverifiedgRPC uses Protocol Buffers serialization on top of HTTP/2, which can reduce payload size by 30–50% compared to JSON and supports server-side streaming.
50%UnverifiedCapabilities that need to be dynamically discovered by AI or triggered by natural-language-described intent are suitable for exposure via MCP; fixed machine-to-machine calls between systems and scenarios with strict requirements on latency or throughput should go directly through traditional APIs such as REST or gRPC.
50%UnverifiedStreaming voice typically relies on bidirectional streaming protocols based on WebSocket or gRPC, or HTTP streaming based on chunked transfer encoding.
50%UnverifiedREST remains the dominant API style, GraphQL is increasingly popular in scenarios requiring flexible queries, and gRPC is widely adopted in microservice communication for its high performance and strongly typed contracts.
50%UnverifiedThe gRPC framework uses protobuf as its default interface description language (IDL)
50%UnverifiedThe proto used by vLLM is typically based on Protocol Buffers (protobuf) and is commonly used in conjunction with the gRPC framework.
50%UnverifiedRPC (Remote Procedure Call) is action-centric, with interfaces directly describing callable functions; common implementations include Google's gRPC (based on Protocol Buffers and HTTP/2) and JSON-RPC.
50%UnverifiedThe same FLARE training code can communicate via local networking in Docker Compose, discover each other via Service in K8s Pods, and exchange model updates via gRPC persistent connections between Slurm job nodes.
50%UnverifiedCortex supports five types of API specifications as input formats: OpenAPI, AsyncAPI, GraphQL, gRPC, and OpenRPC.
50%UnverifiedgRPC uses Protocol Buffers (.proto files) as its interface description language.
50%Unverifiedsystem-design-101 covers topics including communication protocols (REST, GraphQL, gRPC), API design, caching mechanisms, database selection, microservices architecture, DevOps, and cloud-native topics
50%UnverifiedCompared to gRPC, JSON-RPC does not require pre-compiled Protocol Buffer definition files, resulting in a lower development barrier.
50%UnverifiedStarlink设备默认在192.168.100.1地址上通过gRPC接口监听请求，可获取天线状态、信号质量、遮挡数据、GPS坐标等遥测信息
50%UnverifiedStarlink的碟形天线和路由器默认在192.168.100.1地址上监听gRPC请求，可获取天线状态、信号质量、遮挡数据、GPS坐标等遥测信息
50%