Konrad Kowalski (rootsher)Principal Platform & Reliability Architect100000100011100111011101100000101010111100110001

API Design

posts (5)

  1. Realtime in the Browser: From Polling to WebTransport7/7

    Polling, Streaming, SSE, WebSocket, or WebTransport?

    The choice follows from the traffic model: freshness, direction, frequency, ordering and reliability. The simplest correct mechanism usually wins.

  2. series · 7 parts

    Realtime in the Browser: From Polling to WebTransport

    Realtime is a requirement about the maximum acceptable delay of information, not the name of a protocol. The mechanisms from polling to WebTransport, each born…

  3. Ways of Talking to a Backend: From HTML Forms to GraphQL6/6

    GraphQL: Letting the Client Define the Shape of Data

    The response stops belonging to a resource or an operation and starts belonging to the client's query. Flexibility is paid for with predictable execution and…

  4. Ways of Talking to a Backend: From HTML Forms to GraphQL5/6

    RPC: When an API Models Operations Instead of Resources

    RPC starts from the operation, not the resource. Intent becomes explicit, but the semantics move out of HTTP and into the application contract.

  5. series · 6 parts

    Ways of Talking to a Backend: From HTML Forms to GraphQL

    The layers of frontend to backend communication from the bottom up: forms, XHR and fetch start the request, HTTP carries it, and REST, RPC and GraphQL model…