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.
Split the log, keep each key in order
From: The Log: One Record Everyone Can Replay →A topic is split into partitions so many can read and write at once. Records with the same key (a customer id) always land in the same partition, so that customer's events stay in order, though there is no single order across partitions.
Order events arrive, each with a customer id as its key.
Split the work, or each take it all
From: The Log: One Record Everyone Can Replay →Within one consumer group each partition goes to exactly one consumer, so the group shares the load like a queue. A second, separate group reads every record for itself, like pub/sub. One log gives you both patterns.
The topic has 3 partitions. The billing group has 3 consumers.
At-most-once: send it and hope
From: Delivery Guarantees: At-Least-Once, Exactly-Once, and Idempotency →The sender fires one message and never retries. Most of the time it arrives; if the network drops it, it is lost and the sender never finds out. Fast and simple, and never duplicated, for data you can afford to miss.
The sender fires one message and does not wait for any reply.