Question 1

gRPC vs REST, when should I use gRPC?

Accepted Answer

REST: human-readable URLs, universal browser support, simpler debugging, good for public APIs, stateless by design. gRPC: 7-10x faster than REST (binary Protocol Buffers), bidirectional streaming, strong typing with generated code, built-in load balancing. Use gRPC for inter-service communication (Netflix, Uber, Google). Use REST for public APIs, mobile clients, simple CRUD. gRPC-Web bridges browser clients to gRPC backends.

Question 2

What are Protocol Buffers and why are they better than JSON?

Accepted Answer

Protocol Buffers (protobuf): binary serialization format with schema versioning built-in. ~3-10x smaller wire size than JSON, ~3-5x faster to serialize/deserialize. Auto-generates code for 10+ languages. Supports schema evolution: add optional fields, rename fields without breaking old clients. JSON: human-readable, universal, but larger, slower, no built-in versioning. Downside of protobuf: not human-readable (need grpcurl to debug).

Question 3

How do I handle breaking changes in Protocol Buffer schemas?

Accepted Answer

Only additive changes are safe: (1) add new optional fields with default values, (2) rename fields in comments only (field numbers stay same). NEVER: reuse field numbers, remove fields, change field types. Use Buf (buf.build) for breaking change detection, runs CI checks before merge. Tag deprecated fields with `[deprecated = true]`. Always maintain backward compatibility: old clients must work with new server, new clients must work with old server.

Question 4

What is gRPC streaming and why do I need it?

Accepted Answer

gRPC supports 4 RPC modes: (1) Unary: request → response (like REST), (2) Server streaming: request → stream of responses (e.g., video chunks, log tailing), (3) Client streaming: stream of requests → response (e.g., file upload, batch processing), (4) Bidirectional: both sides stream (chat, real-time collaboration). Streaming = lower latency (no request-response round trip), better bandwidth (multiplexed over single HTTP/2 connection), perfect for real-time and large datasets.

Question 5

How do I use gRPC from a web browser?

Accepted Answer

Browsers cannot directly use gRPC (no HTTP/2 over XHR). Three options: (1) gRPC-Web: browser ↔ gRPC-Web proxy ↔ gRPC backend (safest, official support from Buf). (2) grpc-gateway: auto-generate REST endpoints from gRPC protos (easy, best for public APIs). (3) Connect (from Buf): unified gRPC/gRPC-Web/REST semantics (newer, recommended for new projects). All three generate TypeScript stubs, so frontend sees type-safe API calls.

Question 6

What is gRPC reflection and how do I debug services?

Accepted Answer

gRPC reflection lets tools like grpcurl introspect a running gRPC server without .proto files. Server exposes reflection service (enabled by default in most frameworks). Debug with: `grpcurl localhost:50051 list` (list services), `grpcurl localhost:50051 list my.Service` (list methods), `grpcurl -d '{"name":"World"}' localhost:50051 my.Service/Greet` (call a method). BloomRPC (GUI tool) also uses reflection, point it at your server and invoke methods via UI.

Question 7

When should I NOT use gRPC?

Accepted Answer

Don't use gRPC for: (1) public APIs for third parties (use REST/OpenAPI, gRPC not widely adopted outside Google/fintech), (2) IoT/embedded (too heavy, protobuf overkill), (3) request-response latency <5ms (HTTP/2 handshake adds 1-2ms overhead), (4) mobile to backend (use gRPC-Web but complexity rises), (5) simple monolith (gRPC shines at scale; single service = REST is fine). Cost-benefit: gRPC's 7x speed + type safety pays off at 100+ microservices; below that, REST is simpler.

प्रदेश	ज्युनियर	मध्यम	सीनियर
USA	$120k	$165k	$240k
UK	£75k	£110k	£155k
EU	€80k	€115k	€165k
CANADA	C$130k	C$175k	C$260k

gRPC

gRPC म्हणजे काय

📋 सुरू करण्यापूर्वी

💰 प्रदेशानुसार पगार

🎓 प्रमाणपत्रे

⚖ यांच्याशी तुलना करा

❓ FAQ

हे कौशल्य तुमच्यासाठी योग्य आहे का, याची खात्री नाही?

तुमचा आदर्श करिअर मार्ग शोधा