Queues, streams and async processing
Comes up in: Backend design
This concept is being written. It gets the full five steps — explanation, predict, interview angle, practice with tests, and review cards. Here is exactly what it will cover, so you can study it elsewhere in the meantime.
What it covers
- message queues vs logs/streams (e.g. SQS-style vs Kafka-style)
- at-least-once delivery and idempotent consumers
- dead-letter queues
- fan-out
- background jobs and cron
Words you will know
What you will practise
- design an image-processing pipeline
Interview questions this answers
- Why use a message queue? What is at-least-once delivery?