Semicolony ELI5 · comic

gRPC.

Calling a function on another machine as if it were local, using a compact, pre-agreed format instead of plain text.

  1. Dear server, send users.
    { "users": [...] } anyone can read it
    1

    REST mails a plain letter: readable text anyone can open and skim by hand.

  2. Lots of words to parse.
    bulky, slow to parse reading…
    2

    Easy to test, but the envelope is bulky and both sides spend time reading it.

  3. Same rulebook, both ends.
    .proto same rulebook
    3

    gRPC has both sides learn one rulebook first — a shared schema of the messages.

  4. Compact and fast.
    0x1A4F small & fast
    4

    Now they speak a tight binary shorthand: smaller to send, quicker to read.

  5. Like calling next door.
    service A service B getUser() like calling next door
    5

    And it calls a remote function as if it were local — no envelope to address by hand.

  6. Need the rulebook to follow.
    browser 0x1A?! 0x1A4F
    6

    The trade: browsers can’t read the shorthand directly, and you can’t eyeball it.

A plain letter anyone can read, versus two machines speaking a tight private shorthand.
Semicolony semicolony.dev/eli5/grpc/comic
← All ELI5 explainers