How Checkr uses gRPC
summary
Checkr claims gRPC gives stronger service contracts and better documentation and shows the migration path rather than a magic switch. The stack uses a central IDL mono repo, auto-generates language libraries via CircleCI and Gemfury, publishes HTML with protoc-gen-doc, and runs Rails services with the gruf gem. The name‑matcher example returns a boolean and confidence and is deployed; the org has ~500 endpoints and 20+ services, keeps REST for public APIs, and handles errors with gRPC status codes.
AI-written summary · about
chapters (14)
- 0:00Intro
- 2:07What is RPC
- 3:10GRPC IDL
- 6:19Should you use gRPC
- 7:27JSON API
- 8:10What is gRPC
- 10:17Our journey to gRPC
- 11:28Detailed walkthrough
- 12:34Writing the IDL
- 16:26Serving RPC requests
- 19:34Making a RPC request
- 23:50Handling errors
- 27:03Summary
- 28:23Questions
related talks
34mRuby and gRPC
16mgRPC on Ruby on Rails – a perfect match!
21mReal World Migration from HTTP to gRPC in Ruby
41mAdopting gRPC: Overcoming Team and Technical Hurdles
01h 15mREST, GraphQL, and gRPC: A Comparison
35mThe Story of why we migrate to gRPC and how we go about it
07mKeynote: State of gRPC
45mgRPC vs REST: let the battle begin!