Suggest modification to this talk

Title

Description

RailsConf 2019 - How Checkr uses gRPC by Paul Zaich & Ben Jacobson
_______________________________________________________________________________________________
Cloud 66 - Pain Free Rails Deployments
Cloud 66 for Rails acts like your in-house DevOps team to build, deploy and maintain your Rails applications on any cloud or server.

Get $100 Cloud 66 Free Credits with the code: RailsConf-19
($100 Cloud 66 Free Credits, for the new user only, valid till 31st December 2019)

Link to the website: https://cloud66.com/rails?utm_source=-&utm_medium=-&utm_campaign=RailsConf19
Link to sign up: https://app.cloud66.com/users/sign_in?utm_source=-&utm_medium=-&utm_campaign=RailsConf19
_______________________________________________________________________________________________
This is a sponsored talk by Checkr.

Checkr’s mission is to build a fairer future by improving understanding of the past. We are based in San Francisco and Denver. We have found some limitations in only using JSON-based RESTful APIs to communicate between services. Moving to gRPC has allowed us to better document interfaces and enforce stronger boundaries between services. In this session we will share the lessons we have learned while incorporating gRPC into our application, walkthrough setting up a new rails project with gRPC support, and how we plan to expand our usage of gRPC in the future.

Date

Summarized using AI?

If this talk's summary was generated by AI, please check this box. A "Summarized using AI" badge will be displayed in the summary tab to indicate that the summary was generated using AI.

Show "Summarized using AI" badge on summary page

Summary

Markdown supported

In the talk "How Checkr uses gRPC" presented by Paul Zaich and Ben Jacobson at RailsConf 2019, the speakers discuss the challenges faced by Checkr, a background check company, in managing a growing number of internal APIs. They explain how shifting from traditional JSON-based RESTful APIs to gRPC has enhanced their documentation, service boundaries, and overall system resilience. The focus of the talk is on remote procedure calls (RPC) and the advantages of gRPC, which is an open-source framework developed by Google. The speakers outline the following key points:

- **Definition and Context**: RPC (Remote Procedure Call) allows one service to invoke actions on another service. This is essential for Checkr as they have over 500 endpoints and numerous services that must communicate seamlessly.
- **Transition to gRPC**: Historically, Checkr faced issues with undocumented APIs and inconsistent types when using REST. They decided to adopt gRPC to enhance their API management. gRPC provides an IDL (Interface Definition Language), which facilitates precise documentation and better definition of service terms.
- **Comparison with REST and SOAP**: The speakers compare gRPC to traditional methods like SOAP and REST, highlighting the advantages of gRPC in terms of clearly defined APIs and reduced potential errors in service-to-service communication.
- **Implementation Process**: A detailed walkthrough is given on how to set up a new Rails project with gRPC support, using a 'name matcher' service as an example. The process involves writing IDLs, generating code automatically, and deploying services efficiently.
- **Error Handling**: The talk explains how gRPC facilitates structured error handling using status codes, which can provide more clarity on issues during service interactions.
- **Usage of Protocol Buffers**: Implementing protobufs helps enforce message types across services, contributing to a more stable infrastructure.
- **Takeaway Insights**: The presenters emphasize that while gRPC serves well for scaling architectures, REST remains a viable option, especially for smaller or less complex systems. They advocate for a transition that is context-driven, rather than arbitrary, based on the needs and scale of the organization.

In conclusion, Checkr’s journey with gRPC demonstrates the framework's strengths in modernizing API interactions and enhancing internal communication as they scale, with an emphasis on contract-driven development and improving documentation for internal services.

Cancel