wtf( )unctionsystem design, drawn
← all problemsWebSocketsMedium

A socket for a one-way feed

The dashboard shows a live feed, and it was built on a socket because live means socket.

Nothing is ever sent from the client. The feed goes one way, and the choice has bought a connection some proxies will not carry, no automatic reconnection, no built-in resume, a separate scaling story and a hand-written heartbeat — all to support a direction that is never used.

Choose the channel that matches the shape of the traffic.
Components — tap one, then tap a slot on the diagram
?A bidirectional channel costs bidirectional infrastructure. Most feeds only go one way.

Outside every boundary: Six tabs, one host (on HTTP/1.1), Dashboard (never sends), After a drop (resume from where?), Feed service (pushes updates), an empty slot for the the channel this traffic needs Connections: Feed service calls the channel this traffic needs — updates, one way (step 1) the channel this traffic needs calls Dashboard (step 2) Dashboard calls Feed service — never used After a drop controls the channel this traffic needs — on reconnect Six tabs, one host controls the channel this traffic needs

Six tabs, one hoston HTTP/1.1
Dashboardnever sends
After a dropresume from where?
Feed servicepushes updates