Topic
Ann
Learn Ann as a connected topic across chapters, concepts, simulations, and interview reasoning.
10 Concepts14 Articles4h 51m
Overview
Learn Ann as a connected topic across chapters, concepts, simulations, and interview reasoning.
How this topic helps
System Design
Distributed Systems
Ai Agents
Llm
Learning Path in this Topic
Series that contain articles from Ann. Select a path to filter the article list.
Articles
14 matched articles
Article 1ANN Index Types Explained: When to Choose Flat, HNSW, IVF, or IVF-PQTLDR: If your dataset is small and correctness is critical, use Flat. If you need high recall with low latency and enough RAM, use HNSW. If your corpus is huge and memory is your bottleneck, use IVF-P14 min
Article 2ACID Transactions in Distributed Databases: DynamoDB, Cosmos DB, and Spanner ComparedTLDR: ACID transactions in distributed databases are not equal. DynamoDB provides multi-item atomicity scoped to 25 items using two-phase commit with a coordinator item, but only within a single regio39 minArticle 3AI Architecture Patterns: Routers, Planner-Worker Loops, Memory Layers, and Evaluation GuardrailsTLDR: A single agent loop is enough for a demo, but production AI systems need explicit layers for routing, execution, memory, and evaluation. Those layers determine safety, latency, cost, and traceab14 min
Article 4Multistep AI Agents: The Power of PlanningTLDR: A simple ReAct agent reacts one tool call at a time. A multistep agent plans a complete task decomposition upfront, then executes each step sequentially — handling complex goals that require 5-115 minArticle 5Clock Skew and Causality Violations: Why Distributed Clocks LieTLDR: Physical clocks on distributed machines cannot be perfectly synchronized. NTP keeps them within tens to hundreds of milliseconds in normal conditions — but under load, across datacenters, or aft19 minArticle 6Spark Adaptive Query Execution: Dynamic Coalescing, Pruning, and Skew HandlingTLDR: Before AQE, Spark compiled your entire query into a static physical plan using size estimates that were frequently wrong — and a wrong estimate at planning time meant a skewed join, 800 small ta39 minPage 1 of 3