Strategies for separating external api and internal api?

[kost...@gmail.com]

Hey

We are currently using grpc for internal communication between microservices.

We would like to use grpc with grpc-web for FE to BE communication.

Whats the best way to do this without exposing internal data structures that we don't want to be seen by analyzing the generated java script files on the client side?

Ideally we would want to mark "external" messages/service rpc methods and have only those exposed.

Thanks in advance.

[stanle...@google.com]

Currently there's no way to do this using the current grpc-web code generator - it will generate for all messages and methods. I am not aware of any canonical way of marking messages and methods public or private as protobuf syntax.