System design, AI engineering, databases, networking, concurrency and more, written for engineers building real trading and fintech systems — part of the Algomi Suite.
Meera's library app has a very bad term: a dead server, a lost zone, a runaway retry storm, a deleted table and a stolen reservation. Each disaster introduces one idea: SLIs/SLOs, redundancy and failover, circuit breakers and rate limiting, authentication vs authorization, OAuth/OIDC, and recovery targets. Guide 4 of 5.
Created 2026-09-15 · Updated 2026-10-15 · System Design
A monsoon power flicker hits a village ATM just as ₹10,000 slides out. How do you design a withdrawal that survives a network failure between the bank's authorization and the machine dispensing cash, when cash can never be rolled back?
Created 2026-09-16 · Updated 2026-10-15 · System Design
Three zones don't help if they all depend on one shared database. Quorums, static stability, multi-region trade-offs, and why replication isn't a backup.
Created 2026-09-21 · 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
Defending LLM applications against prompt injection and token exhaustion, keeping them up with provider failover, circuit breakers and graceful degradation, and keeping the bill predictable with budgets, routing, and caching.
Created 2026-09-29 · Updated 2026-10-15 · AI Solutions Architecture & AI Engineering
A health check that passes while nobody can reserve a book: how to monitor API outcomes with synthetic journeys and real-request telemetry, keep test traffic safe, turn failures into actionable alerts, and defend the cost, privacy and recovery decisions in an interview.
Created 2026-10-17 · Updated 2026-10-17 · System Design
