O que é gRPC?

Meet gRPC, a high-performance framework for modern APIs. Built for speed and efficiency, it's a great fit for distributed systems and microservices.

RPC (Remote Procedure Call) lets you invoke a function on another machine as if it were local — client sends a request, server runs it and replies.

Imagine calling add(5, 3) when add lives on a remote server. RPC hides every network detail so it feels like a plain local call.

gRPC beats plain REST for internal microservices: faster via HTTP/2 and binary serialization, strongly typed to prevent format errors, and multi-language.

A big reason for gRPC's speed is HTTP/2. Unlike HTTP/1.1's one-at-a-time exchange, HTTP/2 carries many requests and responses over a single connection at once.

HTTP/2 uses binary framing (cheaper to parse than text) and multiplexing, so requests and responses interleave on one connection without blocking.

Protocol Buffers are gRPC's IDL and serialization format. You define services and messages in a .proto file, then compile it into code for many languages.

Quick contrast: REST is resource-oriented over HTTP methods with JSON, while gRPC is service-oriented using Protobuf over HTTP/2 — ideal for internal, high-perf calls.

gRPC wins on four fronts: high performance from HTTP/2 and Protobuf, code generation with strong typing, language-agnostic services, and built-in streaming.

Which of the following are key characteristics or technologies used by gRPC?

You've got gRPC: a high-performance RPC framework on HTTP/2, using Protocol Buffers for interfaces, with speed, strong typing, and language interop. Next: a deeper REST comparison.