grpc-node | gRPC for Node.js -

Code generation plugins have complete freedom to generate whatever code they want. Usually, they try to follow the language's conventions. You'd need to have controls for each language, and most won't provide it.

What are the actual maintenance issues that you are facing? Perhaps there is some other way of solving them.

You can add interceptor in options of your client instance:

After several hours of trial and error, I finally figured out what the problem was, it like many other bugs it turned out to be a stupid one. The order of the tags in the proto file's message has been changed (a new field was added at the top and all of the other fields were pushed downward). The server was using the new definition, while the client was using the old one. When the client tried to call an endpoint, the tags did not match.

All I had to do is re-generate the files for the client stub.

Max suggested contacting Google support or searching in Google cloud forums

For such a case you can use Node.js global

After some research, I did the following steps to resolve the issue

• I was missing node-gyp - which is Node.js native addon build tool. It can be installed by

  npm install -g node-gyp

• Install Python

• Install Visual C++ Build Environment

• Clean up node-modules

• Then do in the folder npm install

The following link talks the above steps in detail: https://github.com/nodejs/node-gyp#on-windows

Definitely you don't need to learn Golang for that. You just need to check how to use gRPC interceptors with node. In the interceptor code you will implement any of those features available in the gRPC middleware for Golang.

It would be something like that

Module version 83 corresponds to Node 14, not 13. Unfortunately, we have not yet published binaries for Node 14, so it's going to be difficult to get that working

Full answer - https://github.com/grpc/grpc-node/issues/1460#issuecomment-638965479

No matter what streaming type the request is, gRPC will use each single connection to open multiple streams. This is one major reason HTTP/2 was chosen as the underlying protocol for gRPC: multiplexing streams onto connections is already part of that protocol.

Of the classes you mentioned, the Channel is the API-level abstraction over connections. A Channel represents any number of connections to backends referred to by the target string. It will automatically establish connections as needed to handle any requests that are initiated.

The Resolver, which you didn't mention, determines what backend addresses are associated with the target string. For example, the DnsResolver will look up DNS records.

A LoadBalancer determines what specific connections to establish and how to distribute requests among those connections. The default load balancing policy, "pick first" just sends all requests to whichever connection is successfully established first. There is also the "round robin" load balancing policy, which tries to establish connections to multiple backends and then cycles through them when starting calls.

A Subchannel represents a connection to a single backend, that can be reestablished if it drops.

The filter stack applies some transformations to requests between when they are initiated at the top-level API and when they are sent out on the network.