High-throughput serverless stream processing
WHAT IT TESTS: stream design at scale. OUTLINE: partition by key for per-user ordering, use a sharded log with batched consumers for backpressure, and tune batch size and shards for cost. RED FLAG: a global FIFO queue or per-event invocation at 100k/sec.
WHAT IT TESTS: designing ordered, backpressure-tolerant, cost-aware stream processing. ANSWER OUTLINE: use a partitioned log such as Kinesis or Kafka, partitioning by user ID so all of a user's events land on one shard and stay ordered; consumers read in batches, giving natural backpressure because the log buffers and consumers pull at their own rate; control cost by tuning batch size, parallelization factor, and shard count rather than invoking per event. RED FLAG: a single global FIFO queue or per-event invocation.
Read the original → interview
- #serverless
- #streaming
- #kinesis
- #ordering
- #scalability
Get five bites like this every day.
Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.