gRPC request context which caries values across microservice boundaries

• konig-kontext

  6 44 6.9 Kotlin

  A globally shared, request scoped, context for JVM based gRPC microservices

  

Both the context and message metadata are already part of gRPC. The gRPC system also allows for server [2] and client message interceptors. Essentially this konig-kontext library provides a interceptor implementations, e.g., [3], that uses their hard-coded key for your serializable context that gets read/written from a gRPC header. The context provided by konig-kontext within your code is a wrapper around the existing gRPC Context [1].

The library is convenient for sure, but I feel that if you had a need to propagate context within gRPC, you'd probably already discovered the API and implemented propagation with your own header keys.

[1] https://grpc.github.io/grpc-java/javadoc/io/grpc/Context.htm...

[2] https://grpc.github.io/grpc-java/javadoc/io/grpc/ServerInter...

[3] https://github.com/konigsoftware/konig-kontext/blob/84faa627...

• InfluxDB

  www.influxdata.com featured

  Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

  

Suggest a related project