Message Queues in Practice
A message queue is a buffer between producer and consumer, and its real job is persistence, ordering, and delivery. This video follows a message from publish to acknowledge: how the broker stores it, how consumers claim it, and what each delivery guarantee actually means when a consumer crashes mid-process.
Topics covered:
- The broker's job: persistence, ordering, and delivery
- At-least-once, at-most-once, and exactly-once semantics
- Consumer groups: how partitions divide work
- Backpressure: what happens when consumers fall behind
- Dead-letter queues and replay: handling poison messages
- Queue vs pub/sub vs stream: picking the right primitive
Related articles
Circuit Breakers and Timeouts: Protecting Services from Cascading Failure
Circuit breaker states — closed, open, half-open — plus timeout budgets and retry limits: the mechanisms that stop cascading failures before they spread.
Background Jobs, Cron, and Queues: Choosing the Right Execution Model
Cron schedules, delayed jobs, and work queues compared: exactly-once vs at-least-once delivery, broker semantics, and when each model fails.
Idempotency Keys and Retry Safety: How APIs Guarantee Exactly-Once
How idempotency keys turn at-least-once delivery into exactly-once effects: key storage, replay windows, concurrency, and idempotency-key header semantics.
More in Backend Engineering
Pagination Strategies
Offset, keyset, and cursor pagination compared by database cost, consistency, and behavior when rows are inserted mid-page.
DetailsCaching for the Service Layer
Service-layer caching done right — cache keys, invalidation, TTLs, and the stampede problem that brings services down.
DetailsWebhooks vs Polling
Webhooks and polling compared at the delivery level — delivery guarantees, retries, and when push is worse than pull.
DetailsDatabase Transactions in Practice
ACID in a real database — write-ahead logs, locks, undo and redo, plus isolation levels and what they change about reads.
DetailsRate Limiting Algorithms, Visualized
Token buckets, leaky buckets, and sliding windows compared by memory, precision, and what they do under burst load.
DetailsAPI Idempotency Keys
How idempotency keys work at the storage level — dedupe tables, unique constraints, and making retries safe for clients.
DetailsBackground Job Processing
Queues, workers, and retries — how background jobs actually execute, from enqueue to acknowledgment, and why they fail.
DetailsREST APIs from the Inside
What happens when a REST API processes a request — routing, deserialization, validation, handlers, and response building end to end.
DetailsConnection Pooling Explained
What a connection pool actually does — the handshake cost it hides, checkout and release mechanics, and how pool size changes latency.
DetailsDepth, delivered weekly
One technical dispatch a week — articles and episode notes before they go public.
One technical dispatch per week. No noise.