grpc transport

[joeblew99]

would you consider GRPC ?

Because there are so many client, i can write my embedded code in c, and my server in go, but they can use the same GRPC service interface. Its agnostic. For IOT thats pretty useful

• GRPC
  • uses little bandwidth resources
  • uses little cpu resources
  • hence is also very low latency
  • developer productivity is high.
  • tools ing is amazing.
• tracing to open tracing
  • https://github.com/grpc-ecosystem/grpc-opentracing
• telemetry to Prometheus
  • https://github.com/grpc-ecosystem/go-grpc-prometheus
• structured logging
  • logrus
• exposure to web using the grpc- gateway. This is an easy way to reuse your GRPC service to have a REST / JSON API, with Swagger.
  • https://github.com/grpc-ecosystem/grpc-gateway
• exposure to web using the proto.js (JS), with the new grpc-bus (golang). This is a way to reuse your GRPC Service to have a web socket based communication with the browser.
  • https://github.com/paralin/grpc-bus