No content

Inspiration ● Idea during a conference ● Obsession with speed and performance ● RPC 

Data representation? 

Architecture 

Spanner ● Fully managed rela=onal database ● Unlimited scale ● Strong consistency ● High availability 

How does it work? 

Interleaving ● Physically co-locates child rows with parent rows 

RPC ● Procedures executed in different address space coded as normal procedure call ● Programmer does not explicitly code the details of the remote interaction ● Typically implemented via a request-response message- passing system 

No content

Representational state transfer ● Standard way of communication between backend-frontend services today ● RESTful systems - stateless and separate concerns of client and server ● A request usually consists of: HTTP verb, header, path to resource, optional message body 

REST vs RPC? ● RPC designed for actions, REST is resource-centric ● RPC executes procedures and commands with ease, works on conectionless or connection- oriented protocols (TCP/UDP) ● REST uses HTTP to communicate (application level protocol) 

gRPC ● Open source high performance RPC ● Runs in any environment ● Efficiently connect services in and across data centers with pluggable support for load balancing, tracing health checking and authentication ● Uses HTTP/2 for transportation and Protocol Buffers as the interface description language 

Load balancing ● Proxy - distributes the RPC call to one of the available backend servers ● Client-side - client aware of multiple backend servers and chooses one 

Protocol Buffers ● Googles interchange format ● Mechanism for serialising destructured data ● Versioning 

Example ● Service ● RPC ● Message 

Architecture? 

Live Demo!