Abstractions and RPC

How this question breaks down

1. 1RPC basicsCore22 minA remote procedure call looks like a local function call, and the stubs and runtime underneath make that true right up until the network fails.
2. 2API stylesCore18 minThree ways to shape the same service's interface (resources over HTTP, typed procedures over HTTP/2, or a queryable graph), each paying for its strengths somewhere else.
3. 3IdempotencyCore22 minMake an operation safe to repeat, so a caller who never heard back can simply try again and still get exactly one effect.

Work through the parts in order and you’ve covered the full design. Each part is one topic.