Getting Started with gRPC and Node.js
summary
Concrete comparisons of modules and outcomes decide whether to watch: grpc uses a C core and compiled add-ons that cause install/debug and compatibility pain; @grpc/grpc-js is a pure-JS, drop-in replacement using HTTP/2 and checks Node >=10; @grpc/proto-loader handles protobuf loading; a community grpc-server-js pure-JS server exists, upstreams fixes, hits ~15–20% faster RPS after simplifications, reaches ~95% test coverage, and shows functional parity with earlier implementations.
AI-written summary · about
chapters (18)
- 0:00Intro
- 0:51How Did I Get Here?
- 2:22One Use Case
- 2:51Introduction to gRPC
- 4:02Features
- 6:06Protocol Buffers
- 8:12RPC and JavaScript
- 13:05Compiled Addons
- 13:28RPC in Pure JavaScript
- 16:40Example Unary Client
- 17:53Example Client Stream
- 18:28Example Server Stream Client
- 18:47Example Bidi Stream Client
- 20:38Introducing gepe-server-js
- 23:19Server Improvements
- 25:39Observed Performance
- 26:11Pain Points
- 28:08Future Work
related talks
25mGetting Started with gRPC and JavaScript
14mLoad Testing gRPC Services in Node.js - Kenny Nguyen, gRPSeek
39mGetting Started with Node.JS
01h 00mNode.js: Faster, Higher, Stronger with GraalVM
33mStrategic Node.js crossroads in 2023
20mFrom Node.js to Go
49mNode JS
40mNode.js: Where are we now, where are we going?