Visualizers

Learn by moving things

Interactive explainers for the ideas behind retrieval, embeddings, and agents. A formula tells you what is true; dragging a vector shows you why. Each one also appears inside the article it belongs to, and runs entirely in your browser, so drag, poke, and break it.

Portrait of Sachin Gupta rendered in binary

The topic fans a copy of each event into a separate queue per subscriber. When the analytics service is slow, its queue backs up while email and SMS keep flowing, unaffected. A slow subscriber is isolated, never a blocker.

A queue per subscriberinteractive
topicemail queue0email serviceSMS queue0SMS serviceanalytics queue0analytics service

Behind the topic, each subscriber has its own queue.

A queue deletes each record the moment it is read; an append-only log keeps every record for a retention window whether or not anyone has read it. That is the one difference the whole idea follows from.

A queue empties, a log remembersinteractive
queue0123deleted once readlog0123kept for the retention windowoffset

Four events arrive. A queue and a log both store them, offsets 0 to 3.

Each reader keeps its own bookmark

From: The Log: One Record Everyone Can Replay

One log, three readers. A live dashboard sits at the newest offset, a recovering job catches up from where it stopped, and a brand-new service resets to offset 0 and replays the whole history. Every reader keeps its own offset.

Each reader keeps its own bookmarkinteractive
01234567oldestnewestlive @ 7catching up @ 7replay @ 7

One log, offsets 0 to 7. Three services will each read it at their own pace.

Visualizers — Sachin Gupta