Build a gRPC-style RPC framework (14 scenes)
Scene 12

Design canvas: configure the RPC stack

Every workload picks a different posture along the dimensions you built, and a coherent stack is one where each choice is defended by the scene that taught it — gRPC wins inside the fleet while REST owns the browser edge.

Previously

Every name you earned — length-prefix, field number, stream, deadline, cancellation, idempotency, interceptor, client-side LB, flow control, QUIC, mTLS — is now a knob; the last move is to set them coherently for a concrete workload and defend each choice with the scene that taught it.

Scene 12

Design canvas: configure the RPC stack

  1. Watch
  2. Try it
  3. Predict
  4. Capture
DESIGN CANVAS · configure the RPC stackworkload CAinternal latency-critical micr…east-west fleet call · p99-sensitiveCODECprotoWIREH2CALLunaryDLINEtightRETRYbud·idemLBc-rrSECmTLSBbrowser-facing public APIa browser or human touches thisCODECJSONWIREH2CALLunaryDLINElooseRETRYbud·idemLBL4SECTLSChigh-throughput telemetry inge…fast producer, never-ending flowCODECprotoWIREH2CALLunaryDLINElooseRETRYraw·NONLBc-rrSECmTLSDcross-datacenter call over a l…long fat pipe, packet loss expectedCODECprotoWIREH3/QUICCALLunaryDLINEtightRETRYbud·idemLBc-rrSECmTLSVERIFIER · cites earlier sceneshigh-throughput telemetry ingestion✓scene 3protobuf in the fleet: typed stubs, schema evolution✗scene 5a never-ending flow needs a streaming call, not unary✗scene 10no stream means no backpressure — producer can OOM✗scene 7retry on a non-idempotent method may double-execute+3 moreSTACK PREVIEWclientstub · protoHTTP/2 · TCPunary · one DATApod 1pod 2pod 3client-side round-robinPRESETconservativebalancedaggressivefor: high-throughput telemetry ingest…Workload C loaded a wrong preset — read the red notes and their scene citations.
What to watch for

This is the whole curriculum on one canvas. Each workload card carries a row of knobs, and every knob is a term you already own — codec, transport, call shape, deadline, retry, load balancing, security. The telemetry card (C) just loaded a preset of unary, loose deadline, and raw unbudgeted retries on a non-idempotent method. Watch the verifier flash red: it cites scene 5 (a never-ending flow should be a streaming call), scene 10 (no stream means no backpressure — the producer can OOM), and scene 7 (raw retries on a non-idempotent method are unsafe). The verifier never just says 'wrong' — it names the scene that taught you why.

Where this sits in Build a gRPC-style RPC framework

Scene 12 of 14, in the Secure & ship act — mTLS identity, then configure the whole stack.. Pick codec, transport, deadline, retry, balancing, and security for four named workloads — each defended by the scene that taught it. gRPC inside the fleet, REST at the edge.

All 14 scenes in Build a gRPC-style RPC framework · Every curriculum

Built with Arqly
Every scene in Build a gRPC-style RPC framework builds on the one before it.All 14 Build a gRPC-style RPC framework scenes