Munander Maan presented an introduction to gRPC, a modern, fast and efficient open-source framework developed by Google. The presentation covered what gRPC is, how it works internally using Protocol Buffers, its advantages over REST APIs, how it achieves scalability, and different types of APIs that can be built with gRPC. The agenda included deep dives into gRPC internals, comparisons with REST, scalability, and API types.

1. Presented By: Munander Maan
Introduction to gRPC
framework and APIs
In gRPC

2. Lack of etiquette and manners is a huge turn off.
KnolX Etiquettes
Punctuality
Respect Knolx session timings, you
are requested not to join sessions
after a 5 minutes threshold post
the session start time.
Feedback
Make sure to submit a constructive
feedback for all sessions as it is
very helpful for the presenter.
Silent Mode
Keep your mobile devices in silent
mode, feel free to move out of
session in case you need to attend
an urgent call.
Avoid Disturbance
Avoid unwanted chit chat during
the session.

3. 01 What is gRPC?
02 gRPC Internals deep dive
03 gRPC vs Rest API
04 Scalability in gRPC
05 Types of API In gRPC
Our Agenda

4. c
What is
gRPC?
gRPC is a Free and
open-source framework
developed by Google.
1. Modern,fast and efficient
2. Supports Streaming
3. Language Independent
4. Uses Protocol Buffers and
HTTP/2

5. OUR MISSIONInsert Your Subtitle Here
1. At the core of gRPC, you need to define the
messages and services using Protocol Buffers.
2. The rest of the gRPC code will be generated
for you and you will have to provide an
implementation for it.
Getting started with
gRPC

6. gRPC Internals
Deep Dive
Understand what gRPC is
really made of ?
C++ Service
Ruby Client
Android java
client
gRPC Server
gRPC
Stub
gRPC
stub
Proto Response
Proto
Request
Proto
Request
Proto
Response

7. 1
2
3
Easy to write message definition
Definition of API is independent
from Implementation
Code can be generated in any
language
Why Protocol
Buffers?

8. • gRPC uses Protocol Buffers for communications.
• Lets measure the payload size vs JSON.
Efficiency of Protocol Buffers over Json

9. STRATEGY INFOGRAPHICInsert Your Subtitle Here
The client & server can
push messages in
parallel over the same
TCP connection.
This greatly reduces
latency. Binary
Servers can push
streams (multiple
messages) for
one request from the
client.
1. Headers can be
compressed.
2. These have much less
impact on the packet
size.
Protocol buffers is a
binary protocol and
makes it s great match
for HTTP/2.
Header Compression
Multiplexing
Server Push
Why HTTP/2

10. How HTTP/2 works?

11. OUR CHARTInsert Your Subtitle Here
gRPC Speaks Your Language

12. gRPC vs Rest API

13. Performance test of gRPC
● https://husobee.github.io/golang/rest/grpc/2016/05/28/golang-rest-v-grpc.html
● Finds that gRPC is 25 times more performant than REST API ( as defined as
time to have the response for an API)

14. Insert Your Subtitle Here01
This means they do not block threads on request02
Therefore each server can serve millions of requests in
parallel03
gRPC clients can be asynchronous or synchronous.04
Google has 10 BILLION gRPC requests being made
per second internally.
Proof of scalability
10 BILLION
Scalability In gRPC
01 gRPC Servers are asynchronous by default.
05
05 gRPC clients can perform client side load balancing

15. OUR CInsert Your S
Types Of API in gRPC

16. DEMO

17. Q/A

18. https://grpc.io/
Reference

19. Thank You !