What is the difference between @EventPattern() and @MessagePattern() in NestJS microservices?

Q: What is the difference between @EventPattern() and @MessagePattern() in NestJS microservices?

// @MessagePattern — return value is sent back to caller @MessagePattern({ cmd: 'find_user' }) async findUser(@Payload() data: { id: number }): Promise { return this.usersService.findOne(data.id); // Caller receives this User object } // @EventPattern — return value is ignored, no reply sent @EventPattern('user_registered') async handleUserRegistered(@Payload() data: UserRegisteredEvent): Promise { await this.emailService.sendWelcome(data.email); // No reply — caller does not wait } // Caller — send() waits for reply const user = await firstValueFrom( this.client.send ({ cmd: 'find_user' }, { id: 1 }), ); // Caller — emit() fire-and-forget this.client.emit('user_registered', { email: 'a@b.com' }).subscribe(); @MessagePattern — use for synchronous query-style operations where the result is needed immediately. @EventPattern — use for domain events signaling something that happened; no response expected. send() blocks the caller until a response is received or a timeout occurs. emit() is non-blocking; the caller continues immediately after the message is sent. Event-based patterns improve resilience — the emitter is decoupled from all consumers and their availability.

Difficulty: 5/10

NestJS decorators, microservice communication patterns, transport layer semantics

@MessagePattern() handles request-response interactions where the return value is sent back to the caller. @EventPattern() handles fire-and-forget events where the return value is discarded. The client uses send() for request-response and emit() for events — both return Observables but with different semantics.

Request-response vs fire-and-forget patterns

Pattern selection guidance:

1
@MessagePattern — use for synchronous query-style operations where the result is needed immediately.
2
@EventPattern — use for domain events signaling something that happened; no response expected.

What is the difference between @EventPattern() and @MessagePattern() in NestJS microservices?

Difficulty: 5/10

NestJS decorators, microservice communication patterns, transport layer semantics

@MessagePattern() handles request-response interactions where the return value is sent back to the caller. @EventPattern() handles fire-and-forget events where the return value is discarded. The client uses send() for request-response and emit() for events — both return Observables but with different semantics.

Request-response vs fire-and-forget patterns

Pattern selection guidance:

1
@MessagePattern — use for synchronous query-style operations where the result is needed immediately.
2
@EventPattern — use for domain events signaling something that happened; no response expected.

What is the difference between @EventPattern() and @MessagePattern() in NestJS microservices?

What is the difference between @EventPattern() and @MessagePattern() in NestJS microservices?

Scenario Questions

Follow-up Questions