History

Manfred Touron 5448f25fd6 glide up		2017-05-18 23:33:43 +02:00
..
client.go	glide up	2017-05-18 23:33:43 +02:00
doc.go	Moved to google.golang.org/genproto/googleapis/api/annotations	2017-03-31 18:01:58 +02:00
encode_decode.go	glide up	2017-05-18 23:33:43 +02:00
README.md	Moved to google.golang.org/genproto/googleapis/api/annotations	2017-03-31 18:01:58 +02:00
request_response_funcs.go	glide up	2017-05-18 23:33:43 +02:00
server.go	glide up	2017-05-18 23:33:43 +02:00

README.md

grpc

gRPC is an excellent, modern IDL and transport for microservices. If you're starting a greenfield project, Go kit strongly recommends gRPC as your default transport. And using gRPC and Go kit together is very simple.

First, define your service using protobuf3. This is explained in gRPC documentation. See add.proto for an example. Make sure the proto definition matches your service's Go kit (interface) definition.

Next, get the protoc compiler. Unfortunately, this needs to be done from source. Fortunately, it's pretty straightforward.

brew install autoconf automake libtool
git clone https://github.com/google/protobuf
cd protobuf
./autogen.sh ; ./configure ; make ; make install

Then, compile your service definition, from .proto to .go.

protoc add.proto --go_out=plugins=grpc:.

Finally, write a tiny binding from your service definition to the gRPC definition. It's a simple conversion from one domain to another. See grpc_binding.go for an example.

That's it! The gRPC binding can be bound to a listener and serve normal gRPC requests. And within your service, you can use standard Go kit components and idioms. See addsvc for a complete working example with gRPC support. And remember: Go kit services can support multiple transports simultaneously.