finds.dev← search

// the find

grpc-ecosystem/grpc-spring

★ 3,708 · Java · Apache-2.0 · updated Oct 2026

Spring Boot starter module for gRPC framework.

A Spring Boot starter that wires gRPC servers and clients into Spring's DI container via @GrpcService and @GrpcClient annotations, with built-in support for Spring Cloud discovery (Consul, Eureka, Nacos), Spring Security, and Sleuth tracing. It's for teams already standardized on Spring Boot who want gRPC without hand-rolling channel/server bean config.

The annotation model (@GrpcService, @GrpcClient) genuinely removes boilerplate - no manual ManagedChannel or server builder wiring, and it plugs into Spring's existing property mechanism (grpc.server.*, grpc.client.*) rather than inventing a new config surface. Discovery integration is real, not bolted on: server-side registration automatically adds the grpc port to the service metadata for Consul/Eureka/Nacos, and the client reads target addresses straight from Spring's DiscoveryClient. Metrics and tracing come for free via micrometer/actuator and Sleuth/Brave if those are already on the classpath, so you're not writing interceptors just to get basic observability. Supporting both grpc-netty and grpc-netty-shaded with automatic preference for the shaded one is a small but practical detail that avoids a class of dependency conflicts larger projects hit.

Anything beyond stock grpc-java stubs (reactive-grpc, grpc-kotlin) needs a custom StubFactory written by hand on the client side - the 'other flavors' support is really just an extension point, not actual support. Using this outside Spring Boot proper requires manual bean configuration, which undercuts the main selling point and makes the plain-Spring path feel like an afterthought. The versioning (3.1.0.RELEASE) doesn't track grpc-java, spring-boot, or spring-cloud versions directly, so compatibility lives in a separate docs table you have to cross-reference before upgrading anything. Documentation is split off-repo onto a GitHub Pages site rather than in the README or Javadoc, so a lot of the actual configuration surface (interceptors, security, testing) isn't visible without leaving the repo.

View on GitHub → Homepage ↗

// want more like this?

We dig through GitHub every week and send a few repos picked for what you actually care about — each with an honest take like this one.

Get finds in your inbox → Search again →