System design, AI engineering, databases, networking, concurrency and more, written for engineers building real trading and fintech systems — part of the Algomi Suite.
Follow one school library's reservation app from a single program to a system with a broker, outbox, saga and read model. Every pattern arrives because a real complaint forces it: monoliths vs microservices, async jobs, queues and streams, delivery guarantees, retries, outbox, sagas, CQRS, event sourcing, and the object patterns inside the code. Guide 3 of 5.
Created 2026-09-15 · Updated 2026-10-15 · System Design
Every Monday at 08:00, 600 schools send progress reports to parents. One Monday some parents get two and some get none. Here is why a job definition, a scheduled run and an execution attempt must be three different records, and why leases don't erase duplicate effects.
Created 2026-09-16 · Updated 2026-10-15 · System Design
Follow one night in a busy sorting office to learn how Kafka stores and replicates messages, what acks and ISR really guarantee, delivery semantics, rebalancing, lag, poison pills, dead-letter queues, and retries with backoff and jitter.
Created 2026-09-29 · Updated 2026-10-15 · System Design
What log compaction actually does inside a Kafka broker: dirty and clean sections, the cleaner's offset map, tombstones and delete.retention.ms, the settings that decide when a record really disappears, and the three interview questions that trip people up.
Created 2026-10-15 · Updated 2026-10-15 · System Design
