{ REST } vs. Battle of API s

Size: px

Start display at page:

Download "{ REST } vs. Battle of API s"

Joseph Parker
5 years ago
Views:

1 { REST } vs Battle of API s

2 Software Engineer at Sensedia Who am I? MBA in java projects Java and microservice enthusiastic

3 Microservices Agenda REST grpc Demo Questions

4 Moving to Microservices Monolith Microservices Feature A Microservice Microservice Feature B Feature C Microservice

5 Challenges with Microservices Communication Security / Authentication Network Communication Speed Language Interoperability

6 Communication Microservice Microservice Microservice HTTP + JSON REpresentational State Transfer BD Microservice Microservice

7 REST - Representational State Transfer GET /movies GET /movies/{movieid} POST /movies PUT /movies/{movieid} DELETE /movies/{movieid}

8 Representational State Transfer Good things Bad things Web already built on top of HTTP Easy to understand Variety of http implementation in any languages Loose coupling between client and server

9 Representational State Transfer Good things Bad things Operations are difficult to model Streaming is difficult to implement Bi-directional streaming is not possible Inefficient, textual representation are not optimal for networks

10 grpc is going to fix all of those problems?

11 Yes!!!

12 What is RPC and grpc?

13 A high-performance open-source universal RPC framework Based on Stubby (Google s internal RPC system) Part of Cloud Native Computing Foundation

14 So what makes grpc so effective?

15 Strongly typed Protocol Buffers Protocol buffers are Google's language-neutral, platform-neutral, extensible mechanism for serializing structured data. Rules for making backwards compatible changes Efficient binary data representation for network transmission Comprehensive style guide

16 syntax = proto3 ; Interface Definition Language The API definition and structure of the payload messages. message PersonRequest { string name = 1; int32 age = 2; } message PersonResponse { int32 id = 1; string name = 2; int32 age = 3; } service PersonService { rpc create(personrequest) returns (PersonResponse); }

17 Define once, generates well-structured code for all supported language!

18 Multiple Language Support Python microservice grpc server Ruby microservice grpc server grpc server grpc Stub grpc Stub Go microservice grpc Stub Java microservice

19 Multiple Platform Support

20 Works over HTTP 2

21 History of HTTP 16 years without evolution or improvement HTTP 0.9 HTTP 1 HTTP 1.1 HTTP

22 HTTP 2 HTTP 2 Multiplexing Bidirectional Streaming HTTPS Performance HTTP 1.x

23 HTTP 2 Multiplexing Bidirectional Streaming HTTPS Performance

24 HTTP 2 Multiplexing Bidirectional Streaming HTTPS SSL/TLS Token authentication Channel credentials Call credentials Performance

25 HTTP 1.1 HTTP 2 Multiplexing Bidirectional Streaming HTTPS Performance HTTP 2

26 Connection options Unary RPC Server streaming RPC Client streaming RPC Bidirectional streaming RPC The client sends a single request and gets back a single response The server sends back a stream of responses after getting the client s request message The client sends a stream of requests to the server instead of a single request The call is initiated by the client calling the method and the server receiving the client metadata, method name, and deadline

27 Who is using grpc?

28 Companies

29 Community

30 Why mainly Google and Netflix are using grpc?

31 Performance Sources:

Performance Sources: https://blog.gopheracademy.

32 Performance Sources:

33 Flexibility & Summary Source:

34 Demo

35 Where to use grpc?

36 Use case Microservices Client-Server Application Integrations and APIs Browser-based Web Applications grpc shines as a way to connect servers in service-oriented environments grpc works just as well in client-server applications, where the client application runs on desktop or mobile devices grpc is also a way to offer APIs over the Internet, for integrating applications with services from third-party providers Do not use! grpc-gateway grpc-web (oct/18)

37 Questions?

38 We're Hiring! sensedia.com/carreira Consultoria P&D Marketing & Sales ADM RH Campinas Rio São Paulo

39 Thanks a million! /larchanjo /luram-archanjo

grpc - A solution for RPCs by Google Distributed Systems Seminar at Charles University in Prague, Nov 2016 Jan Tattermusch - grpc Software Engineer

grpc - A solution for RPCs by Google Distributed Systems Seminar at Charles University in Prague, Nov 2016 Jan Tattermusch - grpc Software Engineer About me Software Engineer at Google (since 2013) Working