This document discusses Google Protocol Buffers (Protobuf), a method for serializing structured data that is faster than JSON or XML. It is well-suited for server-to-server communication where human-readability is not required. Protobuf uses a binary format that allows for higher throughput than technologies like HTTP with JSON. The document also introduces gRPC, which extends Protobuf to provide an RPC framework using Protobuf serialization.

1. Imal Hasaranga Perera
CEO, Treinetic (Pvt) Ltd
www.treinetic.com
Google Protocol Buffers

2. In Simple Terms
It is just another method of Serializing Structured data, you can think of
it as JSON or XML
Json xml
08 -56 01
Protobuf

3. Why Use Another One ?
I already know how to use the most popular JSON / XML formats why
should I worry about this new fancy one ?

4. Server to Server Communication needed.
Server to Server communication format does not need to be human
friendly

5. It is way faster than JSON or XML
Because google uses a binary format protobufs are super fast
0
20
40
60
80
100
120
140
Throughput ( MBs )
GRPC HTTP1.1/ JSON

6. Services in Many Languages ?
Developer : I wrote my REST service in java and now do I have to write a client
in python and Go as well ?, I mean it is not my responsibility !!
Java Server
Go Lang
Client
Python
Client

7. History of ProtoBuf
Google uses a RPC based framework called Stubby which has the ability to
handle
10,000,000,000 RPC calls per second
• In 2008 with the knowledge gained from Stubby they released google
protocol buffers as an open source project.
• However it took almost 8 years since then to release a stable version, in
2017, November Protobuf 3 released as the stable version

8. High-level Architecture
a = 200
Proto File
Wrap
Message
Encode
Message
Java Environment
RPC
Channel
Network UnWrap
Message
Decode
Message
RPC
Channel
C# Environment
a = 200

9. Sample Proto File

10. What is gRPC ?
gRPC is a technology that is extending the protocol buffers and providing RPC
framework
a = 200
Proto File
Wrap
Message
Encode
Message
Java Environment
RPC
Channel
Network UnWrap
Message
Decode
Message
RPC
Channel
C# Environment
a = 200

11. gRPC Cont.
Same IDL as Protobuffer
HTTP 2
Protobuffer 3

12. Cons
Transferring large data is not recommended so if really needed,
developers have to workout mechanism to do it.
There is an incident where hackers were able to reverse the messages
and generate profo file and hack a popular game you have all heard
pokemon go
 Large number of classes and may create confusion with the existing
classes
 throughput is lesser but encoding time may sometimes higher than
json for smaller messages

14. Any Questions ?

15. JSON sends in binary in the network as well so what difference the
protobuffer ?
Size : 13 bytes Size : 3 bytes
8 -56 1123 32 34 97 34 32 58 32 50 48 48 32 125