grpc-spring
grpc-spring copied to clipboard
Spring Boot starter module for gRPC framework.
Is there any idea to make this project AOT compliant (spring-native)? Today I can make it work without problems, but still in runtime and not buildtime.
I have two microservices with common-lib and lib for proto-definition and my grpc client located at common-lib, but it only works with first microservice, where I have GrpcService, in second...
I came across some repeating pattern, a request validation. Clients send a gRPC request and with this functionality just implement `GrpcConstraintValidator` with validation-logic and annotate with `@GrpcConstraint` and the validation...
**The problem** Micrometer provides a metric collection implementation. We should use that instead of reimplementing it ourselves. **The solution** Use the implementation from micrometer. https://github.com/micrometer-metrics/micrometer/pull/2323 We already have an optional...
We are using the spring boot starter to create server and client side implementation for GRPC service. After we start the GRPC server service and use the client the query...
Caused by: io.grpc.netty.shaded.io.netty.util.internal.OutOfDirectMemoryError: failed to allocate 2097152 byte(s) of direct memory (used: 1908408599, max: 1908932608) at io.grpc.netty.shaded.io.netty.util.internal.PlatformDependent.incrementMemoryCounter(PlatformDependent.java:802) at io.grpc.netty.shaded.io.netty.util.internal.PlatformDependent.allocateDirectNoCleaner(PlatformDependent.java:731) at io.grpc.netty.shaded.io.netty.buffer.PoolArena$DirectArena.allocateDirect(PoolArena.java:632) at io.grpc.netty.shaded.io.netty.buffer.PoolArena$DirectArena.newChunk(PoolArena.java:607) at io.grpc.netty.shaded.io.netty.buffer.PoolArena.allocateNormal(PoolArena.java:202) at io.grpc.netty.shaded.io.netty.buffer.PoolArena.tcacheAllocateSmall(PoolArena.java:172) at io.grpc.netty.shaded.io.netty.buffer.PoolArena.allocate(PoolArena.java:134) at...
The current implementation provides a way to add new tags or to replace the entire interceptor bean to customize metrics. The former is a great way to add new static...
Please consider adding properties that users can easily customize for the metric tag names: `service`, `method`, `method.type`, `status.code`.
Please consider adding a property to enable/disable each of the three metric's that are generated for both client & server support. Users might not find utility in one and thus...