@jaigouk

@jaigouk


Let the ideas flow.

Share


Our Newsletter


Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.

Tags


avrt

Twitter


grpc

ping@jaigouk.kim[email protected]

The ultimate glue for microservices

I am playing with grpc on kubernetes in these days. My starting point is
nginx-kubernets-lb. I wanted to start from small and light solution. But heroku was not an option to play with this. So I had to setup kubernetes on aws. I deployed Deis too. It took some time to be able to reproduce the production env. This blog is also running on kubernetes. Now, I am ready to play!

main resources

caution

deploy

https://cloudplatform.googleblog.com/2016/08/gRPC-a-true-Internet-scale-RPC-framework-is-now-1-and-ready-for-production-deployments.html

1. ruby

http://www.grpc.io/docs/quickstart/ruby.html

2. node.js

http://www.grpc.io/docs/quickstart/node.html

3. elixir

https://speakerdeck.com/tony612/the-way-to-grpc-elixir
https://github.com/tony612/grpc-elixir

heroku

https://github.com/kyleconroy/heroku-buildpack-grpc

polyglot

https://github.com/grpc-ecosystem/polyglot

Polyglot is a grpc client which can talk to any grpc server. In order to make a call, the following are required:

  • A compiled Polyglot binary,
  • the .proto files for the service,
  • and a request proto instance in text format.

In particular, it is not necessary to generate grpc classes for the service or to compile the protos into the Polyglot binary.

  • Supports unary, client streaming, server streaming, and bidi streaming rpcs.
  • Runs on Windows, Mac and Linux.
  • Parses proto files at runtime to discover services. Supports pretty-printing discovered services.
  • Supports authentication via oauth.
  • Accepts request protos through stdin and can output responses to stdout to allow chaining.
Comments