From b42f4f4f4108ded7f89d80bed9a0c72fdc4ac013 Mon Sep 17 00:00:00 2001 From: Paul Grosu Date: Tue, 6 Dec 2016 22:04:40 -0500 Subject: submit --- chapter/1/gRPC.md | 14 +++++++++++++- 1 file changed, 13 insertions(+), 1 deletion(-) (limited to 'chapter/1') diff --git a/chapter/1/gRPC.md b/chapter/1/gRPC.md index 4b0c04b..d4f1601 100644 --- a/chapter/1/gRPC.md +++ b/chapter/1/gRPC.md @@ -147,9 +147,21 @@ There are two methods of authentication that are available in gRPC: * SSL/TLS * Google Token (via OAuth2) -gRPC is flexible in that once can implement their custom authentication if that is preferred. +gRPC is flexible in that once can plug in their custom authentication system if that is preferred. +

3.3 gRPC Mechanism

+In its simplest form gRPC has a structured set of steps one goes about using it, which has this general flow: + +1. Download gRPC for the language of interest. + +2. Implement the Request and Response definition in a ProtoBuf file. + +3. Compile the ProtoBuf file and run the code-generators for the the specific language. This will generate the Client and Server endpoints. + +4. Customize the Client and Server code for the desired implementation. + +Most of these will require tweaking the Protobuf file and testing the throughput to ensure that the network and CPU capacities are optimally maximized.

3.3 gRPC Java

-- cgit v1.2.3