gRPC is great when it goes to communication between services. It has many built-in mechanisms to speed up the development process, like auto-generating SDK or streaming support. Seems to be the perfect choice for building your API, right? But in the real world, there are not many public gRPC APIs. REST is still the king. Most gRPC backends expose only the REST API.

The main problem is that gRPC is hard. It is hard to start, it is hard to play with, and even hard to debug. The typical solution for that is to use the REST-to-gRPC translation proxy, like grpc-gateway. That’s not a perfect solution because it complicates the architecture, increases the latency and the maintenance costs.

In this post, I’ll compare a few tools that can help you mitigate those problems. Let’s create a truly gRPC API documentation!

Google Endpoints (Google Smart Docs)

Google Cloud is heavily investing in the gRPC. In this article, we described their Serverless gRPC functions. Google Smart Docs is a free tool to create your API documentation. It can generate the documentation for both REST and gRPC APIs. Moreover, it is free! Here you can find demo documentation. The Smart Docs are an interesting alternative for Swagger UI, but sadly gRPC support is very limited. It generates the gRPC documentation with type descriptions and even the API Authentication schemes but still lacks features like “Try it out” or example values.

Setup

Before proceeding, you have to install the Cloud SDK.

1. Go to Google Cloud Endpoints and click “Create Portal”. It might take a few minutes to create one.
2. Generate the descriptor set for your proto API. Use command: protoc --proto_path=. --include_imports --include_source_info --descriptor_set_out=api_descriptor.pb
3. Create an API specification file.
4. Upload the files: gcloud endpoints services deploy api_descriptor.pb api_config.yaml
5. Visit your documentation portal.

Summary

Google Endpoints is an easy solution if you want private-only documentation and already have configured CI/CD.

GenDocu Cloud

GenDocu Clod is CI/CD solution to build and deliver the gRPC. It automatically subscribes to all the new commits via GitHub and rebuilds the documentation and SDKs. It also generates the SDKs and code-snippets for six programming languages. It also handles the gRPC Web SDK generation. It is possible to define the example values for message structures and authentication schemes. You can also call the endpoints from documentation like in Swagger UI.

Setup

You can also use the demo documentation to explore all the features.

1. Create documentation in GenDocu Cloud Console
2. Pick the SDK’s programming languages
3. Choose the SDK libraries storage - own GitHub repository or GenDocu hosted
4. Select the protobuf Git repository
5. Name your documentation
6. Visit the documentation page https://doc.gendocu.com/<your-nickname>/api/<documentation-name>

Summary

Buf

One of the most popular gRPC tools is the buf CLI - it extends the features known from prototool. The Buf company has created a superb tool and integrated it with its own API Schema Registry. Every schema has its documentation - an example can be found here, here or here.

Setup

1. Install the Buf CLI
2. Authorize the Buf CLI with buf registry login
3. Create a repository on the buf.build webpage
4. Create a configuration file buf config init and reference the repository - the buf.build/
5. Use command build push to create a scheme in the Buf’s registry.

Summary

Buf is not a documentation tool. Nevertheless, it provides decent documentation for your gRPC API.

protoc-gen-doc

There is also a great, open-source project - protoc-gen-doc. It is free and generates the documentation in Markdown, HTML, or JSON. Sadly, it is a protobuf documentation tool - not gRPC. It generates the description of the protobuf structure without even mentioning the gRPC services and methods.

Setup

1. Install it with go get -u github.com/pseudomuto/protoc-gen-doc/cmd/protoc-gen-doc. It is also possible to use dockerized version - more here.
2. Invoke the plugin protoc --doc-opt=html,docs.html <your-protos>
3. Open docs.html file

Summary

It is a good starter for the project - it can be easily adjusted/replaced.

Comparison summary

protoc-gen-doc is fine for internal documentation - it is easiest to set up, but it doesn’t generate the gRPC documentation. You have to host it on your own. It is the only self-hosted option.

GenDocu Cloud is the best to start with as it provides CI/CD out of the box - you can set it up in a minute and requires no maintenance. Great for public and private gRPC API documentation.

Google Endpoints is great if you already have an existing REST API and want to host together with gRPC API - it is the most elastic tool from the comparison but lacks “public mode”.

Buf is the only GenDocu alternative when it goes to public, hosted, gRPC API documentation.

If you find anything missing, please let us know at support[at]gendocu.com