Basics What is gRPC? Design goals Some me the code! HelloWorld gRPC sample and demo gRPC Benefits HTTP/2, Protocol Buffers, multi-language support, connection options Some me more code! Streaming gRPC sample and demo @meteatamel
(RPC) is when a computer program causes a procedure (subroutine) to execute in another address space (commonly on another computer on a shared network), which is coded as if it were a normal (local) procedure call, without the programmer explicitly coding the details for the remote interaction That is, the programmer writes essentially the same code whether the subroutine is local to the executing program, or remote* Remote Procedure Call (RPC) *Wikipedia @meteatamel
does the server expose the service? How does the data serialized/deserialized over the wire? XML, JSON, Binary? What is the nature of the connection? Request/reply, streaming? What about authentication? RPC Questions @meteatamel
++ Exactly how you like it: I did this with Adobe Flex Data Services! -- You need to answer the questions earlier & code 2. Use gRPC: A high performance, open-source universal RPC framework ++ Many of the questions already answered & implemented by community -- You need to buy into gRPC style, gRPC generated code Choices @meteatamel
enough → HTTP verbs (GET, POST, PUT, DELETE etc.) are rich enough → REST semantics are well understood For more complex services where efficiency is important, RPC can help → Domain specific: imagine a bank transfer scenario → More strongly typed experience via stubs → Efficiency with HTTP/2, Protocol Buffer Why not REST? @meteatamel
high performance, open source, general purpose standards-based, feature-rich RPC framework Open sourced version of Stubby RPC used in Google Actively developed and production-ready, current version is 1.3.4 What is gRPC? @meteatamel
the API using Protocol Buffers Client and server code generated from the service definition in 10+ languages Efficiency in serialization with Protocol Buffers and connection with HTTP/2 Connection options: Unary, server-side streaming, client-side streaming, bi-directional streaming Authentication options: SSL/TLS, token based authentication How does it work? @meteatamel
from using proto3 compiler For Java, there is protobuf-maven-plugin for Maven and protobuf-gradle-plugin for Gradl to help For .NET, Grpc.Tools.1.0.1 NuGet package has protoc.exe Step 2: Generate client and server stubs @meteatamel
a blocking or non-blocking client stub with the channel Create a request Send the request using the stub Handle the responses in sync or async mode Step 4: Create client @meteatamel
semantics of HTTP/1.1 Improve end-user perceived latency Address the "head of line blocking" Not require multiple connections Minimize protocol overhead HTTP/2 @meteatamel
within an established connection, which may carry one or more messages. Message is a complete sequence of frames that map to a logical request or response message. Frame is the smallest unit of communication in HTTP/2, each containing a frame header, which at a minimum identifies the stream to which the frame belongs: HEADERS for metadata, DATA for payload, RST_STREAM SETTINGS, PUSH_PROMISE, PING, GOAWAY, WINDOW_UPDATE, etc. HTTP/2 Binary Framing @meteatamel
without blocking on any one Use a single TCP connection to deliver multiple requests and responses in parallel. Enable flow-control, server push, etc. HTTP/2 Request/Response Multiplexing Stream 1 HEADERS Stream 2 DATA Stream 3 HEADERS Stream 3 DATA Stream 1 DATA Stream Y HEADERS Stream X DATA Requests Responses HTTP/2 connection Client Server @meteatamel
indexed list of previously seen header fields Indexes are sent for already seen headers Values are encoded with a static Huffman code HPACK: Header compression for HTTP/2 :method GET :scheme HTTPS :host myhost.com :path /image custom_header some_value :method GET :scheme HTTPS :host myhost.com :path /image custom_header some_value HEADERS Frame :method GET :scheme HTTPS :host myhost.com :path /resource custom_header some_value Request #2 Request #1 :method GET :scheme HTTPS :host myhost.com :path /resource custom_header some_value :path /resource + indexes for already seen values HEADERS Frame @meteatamel
throughput from a single n1-highcpu-16 GPE VM instance, using 9 gRPC channels. More impressive than the almost 3x increase in throughput, is that it took only 1/4 of the CPU resources. 11x difference per CPU 3x increase in throughput https://cloud.google.com/blog/big-data/2016/03/announcing-grpc-alpha-for-google-cloud-pubsub gRPC vs JSON/HTTP for Google Cloud Pub/Sub @meteatamel
of messages to the server using a provided stream. Once the client has finished writing the messages, it waits for the server to read them and return its response. Client streaming Both sides send a sequence of messages using a read-write stream. The two streams operate independently. The order of messages in each stream is preserved. Bi-di streaming Unary RPCs where the client sends a single request to the server and gets a single response back, just like a normal function call. Unary The client sends a request to the server and gets a stream to read a sequence of messages back. The client reads from the returned stream until there are no more messages. Server streaming @meteatamel
meteatamel
.png){kind=avatar}
takahirom
okumin
athug
supurazako
ganchiku
rkaga
htkym
yosuke_furukawa
hananouchi
manfredsteyer
monochromegane
.png){kind=avatar}
yuriko1211
apolaine
szymonslowik
inesmontani
aarron
kneath
moore
eileencodes
hannesfritz
keithpitt
marktimemedia
chikuwait
reverentgeek
