How to Build a Leak-Safe gRPC Frame Decoder Using Reactor Netty

A developer building a custom gRPC runtime on Reactor Netty has detailed the design of a Stage 1 protocol layer: a frame decoder that safely parses gRPC's five-byte message envelope without assuming buffer boundaries align with message boundaries. The decoder uses Flux.defer to give each subscription its own independent decoder instance, preventing shared mutable state across concurrent streams. A deliberate copy-based encoding approach was chosen over zero-copy to make ownership boundaries easier to reason about and verify during cancellation or error scenarios. Every source buffer is explicitly released via doFinally, covering success, failure, and cancellation paths to prevent memory leaks. The author notes the project has advanced beyond this stage, but the ownership and bounded-decoding rules established here remain foundational to subsequent transport layers.