A well designed unified API is essential to creating a reliable cloud service and maintaining that as it grows more complex and micro-services multiply.
We have gRPC for internal micro-service comms, but REST persists for public web as the simplest most compatible and readable protocol.

An approach to solve this is to design a type safe and validated master API in gRPC using its protoc metaprogramming basis. Developers create and evolve a single API, but generate it in multiple languages, and for both gRPC and OpenAPI REST protocols.

This talk outlines this metaprogramming paradigm for API design. DevX practise for API creation and evolution.
Covering the various transcoding options and tools for OpenAPI and which might best suit your purposes.
Including transcoding to streaming and other content types.
Along with how to provide data validation and linting of an evolving API and E2E testing approaches for the transcoded API.