How grpc/grpc-java works
Project type and purpose
• This is a multi-module monorepo hosting gRPC-Java: a Java RPC library and framework.
• Its purpose is to provide a layered RPC stack (Stub → Channel → Transport), plus plugins, sample apps, tests, and build tooling.
File structure
• Top-level build files (.bazel, build.gradle, WORKSPACE) show support for Bazel and Gradle.
• There are dozens of subdirectories each built as an independent module:
• api, stub – the public API and generated client/server stubs
• core – channel logic (load balancing, name resolution, interceptors)
• transport modules – netty, okhttp, inprocess, binder, cronet, xds, s2a, alts, rls, grpclb, etc.
• extensions – auth, authz, census, gcp-observability
• services – channelz, health, reflection
• tools – compiler plugin, examples, benchmarks, testing harnesses, buildSrc, buildscripts
• Each module has its own src/main/java, src/test/java, proto directories for codegen.
README for additional insights
• The README defines three high-level layers: Stub, Channel, Transport.
• It lists supported transports (Netty, OkHttp, In-Process, Binder) and discusses codegen via the compiler plugin.