Introduction to GRPC

On this techtalk, the speaker presented the basic knowledge of open-sourced Remote Procedure Call Framework invented and developed by Google for more than ten years as Client-Server communication framework, GRPC. Beside that, this techtalk also mentioned several benefits of GRPC compared with existing popular client-server communication framework, HTTP/json (REST API)

Transcript

1. gRPC Widya Rarasati Software Engineer Widya Rarasati - Software Engineer
2. What is gRPC? gRPC stands for gRPC Remote Procedure Calls. Open sourced version of Stubby RPC used in Google. https://github.com/grpc/grpc/blob/master/doc/g_stands_for.md
3. Why gRPC? • strict service contracts using Protobuf • data serialization • efficient network communication • Support many common languages: C++, Java, Python, Ruby, Node.js, C#, Go, PHP, Objective-C TL;DR gRPC replace HTTP+JSON.
4. https://www.slideshare.net/borisovalex/enabling-googley-microservices-with-http2-and-grpc
5. What makes gRPC faster • More efficient data encoding data is kept in binary (in client memory and on the wire) • HTTP/2 multiplexed requests over a single connection
6. https://www.slideshare.net/borisovalex/enabling-googley-microservices-with-http2-and-grpc
7. https://www.slideshare.net/borisovalex/enabling-googley-microservices-with-http2-and-grpc
8. https://www.slideshare.net/borisovalex/enabling-googley-microservices-with-http2-and-grpc
9. How To Use gRPC
10. Protobuf as Service Definition
11. Deadline instead of Timeout1 How long the client is willing to wait for an answer. When deadline reached RPC will fail with DEADLINE_EXCEEDED status code response = blockingStub.withDeadlineAfter( deadlineMs, TimeUnit.MILLISECONDS) .sayHello(request);
12. gRPC Deadline1 Deadline are automatically propagated, and can be accessed by the receiver Context context = Context.current(); context.getDeadline().isExpired(); context.getDealine().timeRemaining( MILLISECONDS); context.getDeadline().runOnExpiration(() -> { cleaupResources(); logger.info(“Deadline exceded” ); })
13. gRPC Cancellation When the caller is not interested in the result any more… RPC will fail with CANCELLED status code. Server (receiver) access cancellation status by: streamObserver.isCancelled(); streamObserver.setOnCancelHandler(() -> { cleaupResources(); logger.info(“Call canceled by client.” ); })
14. Reference 1)https://cloudplatform.googleblog.com/2016/08/gRPC-a-true-Internet-scale-RPC-framework-is- now-1-and-ready-for-production-deployments.html 2)https://cloud.google.com/blog/big-data/2016/03/announcing-grpc-alpha-for-google-cloud-pub sub 3)https://www.slideshare.net/borisovalex/enabling-googley-microservices-with-http2-and-grpc 4)https://developers.google.com/protocol-buffers/docs/reference/overview 5)https://grpc.io/blog/deadlines
15. Existing GGB gRPC Implementation PROS CONS Service Contract Manageable contract version No status code for each rpc in protobuf Connection Efficiency Using single TCP connection Infrequently request traffic Logging Can do it in gRPC interceptor Missing readability of HTTP request traffic
16. Other things about gRPC: - Channel https://github.com/grpc/grpc/blob/master/doc/connectivity-semantics-and-ap i.md - Reflection Server https://github.com/grpc/grpc-go/blob/master/Documentation/server-reflectio n-tutorial.md - Client cancel StreamObserver<HelloResponse> response = blockingStub.sayHello(request); ((ClientCallStreamObserver) response.).cancel()
17. Thank You