gRPC
ConceptProductSince version 1.1.0
Product guide: what the capability brings, for whom, its limits and the version that delivered it - no configuration syntax.
| What it does | Serves a gRPC service from its .proto alone, three ways: native gRPC, gRPC-Web for a browser, and REST/JSON at the routes its standard annotations declare. A method is one operation, whatever protocol it comes in through |
| Why it matters | A team writes a gRPC service and offers it to a web client or a REST partner without writing a translation gateway. Same identity, same quota, same audit, whatever the door |
| Use cases | Expose an internal gRPC service to a web application; publish a REST API generated from the .proto; relay a gRPC server stream as SSE |
| Limits | Client and bidirectional streams stay served in gRPC only, not in REST; some REST annotation shapes are refused at load (variables spanning segments, verbs) |
| Since | 1.1.0 |
| Configure | A gRPC upstream |