gRPC
A high-performance remote procedure call framework that generates client and server code from Protocol Buffers definitions and runs over HTTP/2.
In more detail
It offers compact binary messages, deadlines and streaming in both directions, which suits calls between services a team controls. Browsers and ordinary HTTP tools support it poorly, so public web clients often need a translation layer.
Examples
The course lists it with HTTP as a better fit than Kafka for request-reply.The course collector accepts OTLP over gRPC on port 4317.Related terms
- RPC — A remote procedure call: calling a function in another program over a network as if it were a local function call.
- Protocol Buffers — A language-neutral way to define data structures and services in .proto files and encode messages in a compact binary format.
- HTTP/2 — A version of HTTP that sends the same methods, statuses and headers in a binary format and runs many requests at once over one connection.
- code generation — Producing client or server code automatically from a machine-readable contract such as an OpenAPI document or a Protocol Buffers file.
- request-reply — An interaction where the caller sends a request and waits for a single reply before continuing.
- microservice — A small, independently deployed service that owns one business capability, such as billing or notifications.
- OTLP — The OpenTelemetry Protocol: the standard way to send traces, metrics and logs between services, collectors and telemetry backends.
- receiver — The part of a collector pipeline that accepts incoming telemetry in a given protocol.
Taught in
- What An API Is, And The Alternatives — Modern API Architecture: REST, GraphQL & gRPC
- When Each Wins: REST, GraphQL, gRPC And SOAP — Modern API Architecture: REST, GraphQL & gRPC
- Running, And Still Down — Certified Kubernetes Application Developer (CKAD) Exam Prep
- Probes And Health Checks — Certified Kubernetes Application Developer (CKAD) Exam Prep
- When Kafka Is The Wrong Tool — Apache Kafka & Event Streaming
- Pin It, Lint It, Prove It: Images And Runtimes — Kubernetes and Cloud Native Associate (KCNA) Exam Prep
- Who Decides What Ships: The CNCF And Its Community — Kubernetes and Cloud Native Associate (KCNA) Exam Prep
- Native HTTP/2 Protocols: Multiplexed Streams & Push — Node.js Internals & Backend Services
- The OpenTelemetry Collector — Full-Stack Observability: Metrics, Tracing & Logging
- Fifteen Traces For Six Bookings: Where Context Was Lost — OpenTelemetry Certified Associate (OTCA) Exam Prep
- Nine Lines, Five Bugs: Configuring The SDK — OpenTelemetry Certified Associate (OTCA) Exam Prep
- Validated And Deaf: Checking A Collector Config — OpenTelemetry Certified Associate (OTCA) Exam Prep
- Which Node Was It? Collector Deployment Patterns — OpenTelemetry Certified Associate (OTCA) Exam Prep
- Two Replicas, Half A Trace: Scaling The Collector — OpenTelemetry Certified Associate (OTCA) Exam Prep
- Collector Sprint: Sixteen Predictions — OpenTelemetry Certified Associate (OTCA) Exam Prep
- Failed Twice, Flushed Fine: Error Handling And Schemas — OpenTelemetry Certified Associate (OTCA) Exam Prep
- Forty Four Of Sixty: The Mock And What It Tells You — OpenTelemetry Certified Associate (OTCA) Exam Prep
- The Evening Before: Final Review — OpenTelemetry Certified Associate (OTCA) Exam Prep