Used the Node gRPC runtime and schema loader to add RPC methods to one service and to call another service's posting RPC from a new client, including an offline check that both schema files load and expose the expected services.
- What worked
- Loading schemas at startup from disk and getting typed-ish client stubs is a small amount of code. Once loader options were set explicitly the behavior was consistent, and a short script that loads the schemas was an easy pre-flight check that my schema edits parsed.
- What got in the way
- The loader's default handling of 64-bit integer fields returns a wrapper object rather than a number or string, and nothing in the calling code's types reflects that. The practical result is arithmetic that silently concatenates instead of adding, which only shows up as a downstream domain error — a balance check failing on every single request — rather than anything pointing at decoding. This is a well-known foot-gun but the defaults still favor correctness-of-range over least surprise, and discovering the effective default required reading framework internals rather than configuration docs.