Review cards · 18 cards
Streaming
Logs like Kafka, partitions and ordering, windows and aggregations over events.
Cards
- Which job is fine as a daily batch rather than a stream?
- A Kafka topic has 12 partitions, and a consumer group has 20 consumers. How many of them receive messages?
- Kafka keeps messages after consumers read them. What does that make possible?
- A topic must take 300 MB/s, and one consumer instance can process about 10 MB/s. How many partitions does the topic need so consumers keep up?
- Counting events in fixed, non-overlapping one-minute buckets (12:00–12:01, 12:01–12:02, …) uses a _____ window. A "last 5 minutes, updated every minute" count uses a _____ window.
- Why do analytics windows usually use event time rather than processing time?
- What ordering does Kafka guarantee, and how do you keep one user's events in order?
- A Kafka topic with _____ keeps at least the latest message for each key and removes older ones, so the topic stays a complete snapshot of current values.
- A Kafka consumer can commit its offset before or after processing a message. What does each give you?
- A million view events a second must update per-video counts. Why aggregate in the stream before writing to a database?
- A Kafka cluster takes 50 MB/s, keeps data for 7 days, and stores 3 replicas. How much disk does that need?
- You want to group each user's clicks into visits that end after 30 minutes without a click. Which window fits?
- What is change data capture (CDC), and why use it to keep a search index in sync?
- A stream job keeps counts in memory. How does it recover after a crash without double-counting?
- In a Kappa architecture (stream processing only, no separate batch layer), how do you recompute results after fixing a bug?
- An event arrives after its window's result was already emitted. What can a stream job do with it?
- A consumer joins a Kafka consumer group and partitions are rebalanced. What can that cause?
- A stream processor's running estimate that no more events older than time T will arrive is called a _____. Events older than it that arrive anyway are _____.
More topics
- Estimation 21 cards
- Networking 16 cards
- API design 17 cards
- Caching 21 cards
- Databases 22 cards
- Replication 15 cards
- Sharding 18 cards
- Consistency 19 cards
- Queues 18 cards
- Availability 14 cards
- Resilience 16 cards
- Storage 14 cards
- Realtime 15 cards
- Data structures 16 cards
- Security 17 cards
- Observability 18 cards
- Coordination 16 cards