Redis transport in NestJS - Step-by-Step Execution

Concept Flow - Redis transport

NestJS Microservice Setup

↓

Configure Redis Transport

↓

Connect to Redis Server

↓

Send/Receive Messages

↓

Handle Messages in Handlers

↓

Process Response or Event

↓

End

This flow shows how a NestJS microservice uses Redis transport to connect, send, receive, and handle messages.

Execution Sample

NestJS

const app = await NestFactory.createMicroservice(AppModule, {
  transport: Transport.REDIS,
  options: { url: 'redis://localhost:6379' },
});
await app.listen();

This code creates a NestJS microservice using Redis transport and connects to a Redis server.

Execution Table

Step	Action	Evaluation	Result
1	Create microservice with Redis transport	Transport.REDIS and options.url set	Microservice instance created, ready to connect
2	Connect to Redis server	Attempt connection to redis://localhost:6379	Connection established successfully
3	Listen for messages	Waiting for incoming messages	Microservice ready to receive messages
4	Receive message from client	Message received on Redis channel	Handler invoked with message payload
5	Process message in handler	Handler logic executed	Response or event sent back via Redis
6	Send response/event	Message published to Redis channel	Client receives response or event
7	Microservice continues listening	Loop back to waiting for messages	Ready for next message
8	Shutdown microservice	Stop listening and disconnect	Redis connection closed, microservice stopped

💡 Microservice stops when shutdown is called or process ends

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 4	After Step 6	Final
app	undefined	Microservice instance	Connected instance	Listening instance	Response sent	Closed

Key Moments - 3 Insights

Why does the microservice need the Redis URL in options?

The Redis URL tells the microservice where to connect. Without it, the connection cannot be established (see Step 2 in execution_table).

What happens if the Redis server is not running when connecting?

The connection attempt will fail, and the microservice cannot listen or send messages. This stops progress at Step 2.

How does the microservice know when a message arrives?

It listens on Redis channels and triggers handlers when messages arrive (Step 4 and 5). This is automatic after connection.

Visual Quiz - 3 Questions

Look at the execution_table, what is the state of 'app' after Step 2?

A Response sent

B Microservice instance created but not connected

C Connected instance

D Closed

💡 Hint

Check variable_tracker column 'After Step 2' for 'app' value

At which step does the microservice start listening for messages?

A Step 3

B Step 1

C Step 5

D Step 7

💡 Hint

Look at execution_table row describing 'Listen for messages'

If the Redis URL is incorrect, which step will fail?

A Step 1

B Step 2

C Step 3

D Step 6

💡 Hint

Connection to Redis server happens at Step 2

Concept Snapshot

NestJS Redis Transport Quick Guide:
- Use Transport.REDIS in microservice options
- Provide Redis URL (e.g., redis://localhost:6379)
- Microservice connects to Redis server
- Listens and sends messages via Redis channels
- Handlers process incoming messages
- Shutdown closes Redis connection cleanly

Full Transcript

This visual execution trace shows how a NestJS microservice uses Redis transport. First, the microservice is created with Redis transport and a Redis URL. Then it connects to the Redis server. Once connected, it listens for messages on Redis channels. When a message arrives, the handler processes it and sends a response or event back through Redis. The microservice continues listening until it is shut down, which closes the Redis connection. Key points include the importance of the Redis URL for connection, the automatic listening for messages after connection, and the message handling flow.