We concluded the last article by generating a gRPC Gateway service to act as a proxy in front of our gRPC chat service. This service would convert familiar REST/HTTP requests from clients to/from our gRPC services. We also briefly discussed how the protoc
utility orchestrates various plugins to generate various artifacts: solely via stdin
and stdout
.
In the same vein, our REST/HTTP gateway was generated by using the grpc-gateway
plugin and annotating our RPC methods by http
method, bindings, and parameter details (for further customization). We also generated OpenAPI specs for our generated gateway service so it could be consumed via the SwaggerUI, too.