gRPC vs REST - API Strat 2016

Sandeep Dinesh Developer Advocate @sandeepdinesh vs {REST}

@sandeepdinesh Who has heard of gRPC?

@sandeepdinesh Who is using gRPC?

5 gRPC REST

6 gRPC REST

@sandeepdinesh gRPC is basically Protobuf over HTTP/2 POST

@sandeepdinesh REST is basically JSON over HTTP 1.1

@sandeepdinesh JSON → Protobuf HTTP 1.1→ HTTP/2

@sandeepdinesh JSON vs Protobuf plaintext vs binary human readable vs
machine readable repetitive vs compressed fast (de)serialization vs faster (de)serialization* Everything supports it vs limited support

@sandeepdinesh HTTP 1.1 vs. HTTP/2 plaintext vs binary no pipelining
vs native pipelining new connection per request vs persistent TCP connection repetitive vs compressed polling vs streaming Non-secure by default vs TLS by default Everything supports it vs limited support

@sandeepdinesh Let’s Benchmark!

@sandeepdinesh

@sandeepdinesh us-west1-a us-east1-c Data B46 Data B64

@sandeepdinesh Make 10,000 “Simultaneous Requests” See how fast the server
can process them all

@sandeepdinesh https://commons.wikimedia.org/wiki/File:Rabbit_Looks_Surprised_by_Monique_Haen.jpg Rabbit Hole

@sandeepdinesh Three endpoints REST Non-Streaming gRPC Bidirectional Streaming gRPC Fast?
Faster? Fastest?

@sandeepdinesh us-west1-a us-east1-c Node.js Client Node.js Server

@sandeepdinesh Node.js is async, but single threaded Go has true
multithreading

@sandeepdinesh Node.js uses a C driver for gRPC Go uses
a native Go driver

@sandeepdinesh us-west1-a us-east1-c Go Client Go Server Node.js Client Node.js
Server

@sandeepdinesh BENCHMARKS https://public.tableau.com/shared/N4YBPFJ7W?:display_count=yes

@sandeepdinesh us-west1-a us-east1-c 1

@sandeepdinesh Make 10,000 Ping-Pongs over the “same” connection

@sandeepdinesh Cheating!

@sandeepdinesh 12 Server Methods 12 Client Methods 2 Languages 3
Datacenters

@sandeepdinesh gRPC is consistently faster

@sandeepdinesh Introducing gRPC into your microservices

@sandeepdinesh Clients REST Server v1 REST Server v2 gRPC Server
v3 REST REST gRPC??? WTF MATE?

@sandeepdinesh 1) Force clients to upgrade or use the old
service 2) Create gRPC and REST endpoints for the new service

@sandeepdinesh 1) Force clients to upgrade or use the old
service 2) Create gRPC and REST endpoints for the new service https://commons.wikimedia.org/wiki/File:Carrot-fb.jpg https://pixabay.com/en/photos/wooden%20stick/ >

@sandeepdinesh message Person { enum PhoneType { MOBILE = 0;
HOME = 1; WORK = 2; } message PhoneNumber { string number = 1; PhoneType type = 2; } string name = 1; int32 id = 2; string email = 3; repeated PhoneNumber phone = 4; } { "name": "‘Sandeep’", "id": 123, "email": "‘[email protected]’", "phone": [ { "number": 1234566543, "type": "‘HOME’" }, { "number": 1234566545, "type": "‘MOBILE’" } ] }

@sandeepdinesh gRPC Gateway!

@sandeepdinesh

@sandeepdinesh syntax = "proto3"; package pingpong; service PingPong { rpc
SyncPerson (Person) returns (Base64) {} }

@sandeepdinesh syntax = "proto3"; package pingpong; import "google/api/annotations.proto"; service PingPong
{ rpc SyncPerson (Person) returns (Base64) { option (google.api.http) = { post: "/addperson" body: "*" }; } }

@sandeepdinesh

@sandeepdinesh Bonus: Swagger!

@sandeepdinesh REST isn’t “dead”

@sandeepdinesh gRPC give you additional capabilities like streaming, consistency, and
tooling

@sandeepdinesh gRPC Gateway is an easy way to provide backwards
compatibility

@sandeepdinesh

@sandeepdinesh Use HTTP/2 There is no excuse!

@sandeepdinesh Thanks! gRPC: grpc.io gRPC Gateway: github.com/grpc-ecosystem/grpc-gateway Benchmark Charts: public.tableau.com/profile/sandeep.dinesh

gRPC vs REST - API Strat 2016

gRPC vs REST - API Strat 2016

More Decks by Sandeep Dinesh

Other Decks in Technology

Featured

Transcript