REST vs gRPC: Battle of API's
Download as PPTX, PDF1 like961 views
This document compares REST and gRPC for microservices communication. It discusses how gRPC addresses limitations of REST like inefficient binary encoding and lack of bidirectional streaming. gRPC uses protocol buffers for interface definition and code generation. It supports multiple languages and platforms and uses HTTP/2 for performance. Companies like Google and Netflix use gRPC for its performance advantages. The document provides examples of unary, server streaming, client streaming and bidirectional streaming RPC calls in gRPC. It recommends using gRPC for microservices and client-server applications where performance is important.
Ad
More Related Content
What's hot (20)
Similar to REST vs gRPC: Battle of API's (20)
Ad
Recently uploaded (20)
![Get & Download Wondershare Filmora Crack Latest [2025]](https://cdn.slidesharecdn.com/ss_thumbnails/revolutionizingresidentialwi-fi-250422112639-60fb726f-250429170801-59e1b240-thumbnail.jpg?width=560&fit=bounds)
Ad
REST vs gRPC: Battle of API's
- 1. { REST } vs Battle of API’s
- 2. Who am I? ● Software Engineer at Sensedia ● MBA in java projects ● Java and microservice enthusiastic
- 3. Agenda ● Microservices ● REST ● gRPC ● Demo ● Questions
- 4. Moving to Microservices Feature A Feature B Feature C Monolith Microservice Microservice Microservices Microservice
- 5. ● Communication ● Security / Authentication ● Network Communication Speed ● Language Interoperability Challenges with Microservices
- 6. Communication Microservice Microservice Microservice HTTP + JSON REpresentational State Transfer Microservice Microservice BD
- 7. REST - Representational State Transfer GET GET POST PUT DELETE /movies /movies/{movieId} /movies /movies/{movieId} /movies/{movieId}
- 8. ● Web already built on top of HTTP ● Easy to understand ● Variety of http implementation in any languages ● Loose coupling between client and server Representational State Transfer ● Good things ● Bad things
- 9. ● Operations are difficult to model ● Streaming is difficult to implement ● Bi-directional streaming is not possible ● Inefficient, textual representation are not optimal for networks Representational State Transfer ● Good things ● Bad things
- 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 ● Rules for making backwards compatible changes ● Efficient binary data representation for network transmission ● Comprehensive style guide Protocol Buffers Protocol buffers are Google's language-neutral, platform- neutral, extensible mechanism for serializing structured data.
- 16. Interface Definition Language The API definition and structure of the payload messages. syntax = “proto3”; 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. Ruby microservice gRPC server Go microservice gRPC server gRPC Stub Java microservice gRPC Stub Python microservice gRPC server gRPC Stub Multiple Language Support
- 20. Works over HTTP 2
- 21. History of HTTP HTTP 0.9 1991 HTTP 1 1996 HTTP 2 2015 HTTP 1.1 16 years without evolution or improvement 1999
- 22. HTTP 2 ● Multiplexing ● Bidirectional Streaming ● HTTPS ● Performance HTTP 2 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 2 ● Multiplexing ● Bidirectional Streaming ● HTTPS ● Performance HTTP 1.1 HTTP 2
- 26. Connection options The client sends a single request and gets back a single response Unary RPC The server sends back a stream of responses after getting the client’s request message Server streaming RPC The client sends a stream of requests to the server instead of a single request Client streaming RPC The call is initiated by the client calling the method and the server receiving the client metadata, method name, and deadline Bidirectional streaming RPC
- 27. Who is using gRPC?
- 28. Companies
- 29. Community
- 30. Why mainly Google and Netflix are using gRPC?
- 33. Flexibility & Summary Source: https://www.infoq.com/presentations/grpc
- 34. Demo
- 35. Where to use gRPC?
- 36. Use case gRPC shines as a way to connect servers in service- oriented environments Microservices gRPC works just as well in client- server applications, where the client application runs on desktop or mobile devices Client-Server Application gRPC is also a way to offer APIs over the Internet, for integrating applications with services from third-party providers Integrations and APIs Do not use! grpc-gateway grpc-web (oct/18) Browser-based Web Applications