Key Technology Deep Dives: DynamoDB, Temporal & ZooKeeper
Three technologies interviewers love to probe once you name them: DynamoDB (keys, single-table design, GSI vs LSI, partition limits, transactions, DAX, Streams, global tables), Temporal durable execution (workflows vs activities, deterministic replay, versioning, history limits, when it beats saga + outbox), and ZooKeeper (ZAB, znodes, one-shot watches, recipes, and why Kafka and Kubernetes moved to KRaft and etcd).
About 130 minutes · 17 exam questions · 12 interview questions · 2 code labs
What you will learn
- Using a key technology in an interview: ask, justify, bound, and have a neutral fallback
- DynamoDB data model: partitions, keys and the capacity arithmetic
- Single-table design: pre-joining data around access patterns
- GSI vs LSI: the decision you cannot easily undo
- Throughput in practice: partition limits, burst, adaptive capacity and hot keys
- Transactions, conditional writes and idempotency in DynamoDB
- DAX, Streams and global tables: the caveats interviewers dig for
- When NOT to use DynamoDB
- Temporal and durable execution: workflows, activities, event history and replay
- Temporal determinism, versioning and history limits
- Temporal signals, queries, updates, retries and timeouts, and when a workflow engine beats saga + outbox
- ZooKeeper internals: ZAB, znodes, sessions and the real semantics of watches
- ZooKeeper recipes done right, why the world moved to KRaft and etcd, and when ZooKeeper is the wrong tool
Previous: Object & File Storage · Next: AI/LLM Fundamentals for Engineers: Transformers, Fine-tuning vs RAG vs LoRA, and Agent Protocols