Course outline

01 · HTTP & REST APIs

02 · Databases & Persistence

03 · Authentication & Authorization

04 · API Design & gRPC

05 · Caching, Queues & Background Jobs

06 · Production-Ready Services

07 · Advanced Auth & Tenant Security

08 · Performance & Caching at Scale

09 · Testing & Release Confidence

Stage 3 · Build

Caching, Queues & Background Jobs

Message Queues

Compare RabbitMQ, NATS, Kafka, and Redis Streams for durability, ordering, and delivery guarantees.

8 min readBuilding Backend ApplicationsBuild

Why Message Queues

Message queues decouple producers from consumers. A service publishes a message and continues. Workers process messages asynchronously. This improves resilience, scalability, and response time.

RabbitMQ

RabbitMQ is a traditional message broker with exchanges, queues, and routing keys. It supports multiple protocols and provides strong delivery guarantees. Best for task queues and work distribution.

Gopublishing-to-rabbitmq.go

18 linesLn 1, Col 1Go

RabbitMQ uses exchanges to route messages to queues. The routing key determines which queue receives the message. DeliveryMode.Persistent ensures messages survive broker restarts.

NATS

NATS is a lightweight, high-performance messaging system. It supports pub/sub, request-reply, and queue groups. NATS JetStream adds persistence, exactly-once delivery, and consumer groups.

Gonats-jetstream.go

25 linesLn 1, Col 1Go

NATS JetStream provides persistence with minimal overhead. Streams store messages. Consumers read messages. Queue groups distribute work across instances.

Kafka

Kafka is a distributed event streaming platform. It stores messages in partitions on disk. Consumers track their position with offsets. Best for event sourcing, log aggregation, and high-throughput streaming.

Gokafka-producer-and-consumer.go

30 linesLn 1, Col 1Go

Kafka guarantees ordering within a partition. Messages are retained for a configurable time. Consumers track their offset to know which messages they have processed.

Redis Streams

Goredis-streams.go

36 linesLn 1, Col 1Go

Redis Streams combine the simplicity of Redis with Kafka-like features. Consumer groups distribute work. XACK confirms processing. Messages persist to disk.

Choosing a Queue

Queue	Best For	Delivery	Complexity
RabbitMQ	Task queues, routing	At-least-once	Medium
NATS	Lightweight pub/sub	At-most-once / JetStream	Low
Kafka	Event streaming, high throughput	At-least-once / exactly-once	High
Redis Streams	Simple streaming with existing Redis	At-least-once	Low

Start with Redis Streams

If you already use Redis, Redis Streams are the simplest way to add async processing. For more advanced needs (partitioning, retention), graduate to Kafka or RabbitMQ.

Mark this lesson complete to store local progress and unlock a cleaner resume path the next time you visit.