- Property Manager name: Google Remote Procedure Call (gRPC)
- Behavior version: The
latestrule format supports thegRPCbehavior v1.1. - Rule format status: Beta, possible breaking changes
- Access: Read/Write
- Allowed in includes: Not available for
latestrule format - Recent changes:
- The gRPC behavior is now in general availability. Also, support for gRPC-Web text translation has been added.
This behavior enables support for native gRPC (Google Remote Procedure Call). Akamai supports gRPC-Web by default. Confirm with your account representative that your contract enables the gRPC behavior.
The gRPC framework is an open-source, high-performance Remote Procedure Call (RPC) that uses protocol buffers (protobuf) to transmit data. Protobuf messages are small, fast, and support a wide range of programming libraries and tooling.
You can use gRPC to enable function calls across processes and connect large numbers of microservices. It's built on HTTP/2, supports multiplexed streams, and four communication patterns: request-response, server streaming, client streaming, and bidirectional streaming.
| Option | Type | Description | Requires | |
|---|---|---|---|---|
enabled | boolean | Enables HTTP/2, multiplexed streams, and concurrent RPCs over a single connection. | {"displayType":"boolean","tag":"input","type":"checkbox"} | |
enableBidirectionalStreaming | boolean | Whether to send many messages per request and per response, concurrently and independently, over a single long-lived connection. | {"displayType":"boolean","tag":"input","type":"checkbox"}{"if":{"attribute":"enabled","op":"eq","value":true}} | |
translateWebRequestToNative | boolean | Enable this to upgrade all gRPC-web requests to native gRPC at the edge. | {"displayType":"boolean","tag":"input","type":"checkbox"}{"if":{"attribute":"enabled","op":"eq","value":true}} |
