Questions
24 of 25
1What is the difference between request-response and event-based (fire-and-forget) message patterns in NestJS microservices?
2What is the @Payload() decorator and how do you use @Ctx() to access transport-specific context in NestJS microservices?
3How do you connect a NestJS microservice to RabbitMQ?
4How do you implement manual message acknowledgement with RabbitMQ in NestJS?
5How do you implement a RabbitMQ topic exchange for routing messages to multiple queues based on routing keys in NestJS?
6How does gRPC differ from REST and when would you choose it for inter-service communication in NestJS?
7How do you implement an API Gateway pattern in NestJS that aggregates multiple microservices?
8How do you implement distributed tracing across NestJS microservices?
9What transport layers does NestJS support for microservices and how do you bootstrap a microservice?
10How do you connect a NestJS microservice to Apache Kafka?
11How do you handle Kafka message patterns and access message headers and partition info via KafkaContext in NestJS?
12How do you set up gRPC in a NestJS microservice?
13How do you implement a circuit breaker pattern when calling a downstream microservice in NestJS?
14How do you inject and use a ClientProxy to communicate with another microservice in NestJS?
15How do you handle errors in microservice request-response patterns and propagate them to the caller in NestJS?
16How do you implement Kafka consumer groups and what guarantees does partition assignment give you in NestJS?
17How do you implement the outbox pattern with Kafka in NestJS to guarantee exactly-once message delivery?
18How do you implement gRPC streaming including server-side, client-side, and bidirectional streaming in NestJS?
19What is the difference between @EventPattern() and @MessagePattern() in NestJS microservices?
20How do you implement the Saga pattern for distributed transactions across NestJS microservices?
21How do you implement idempotent event handlers to safely handle duplicate message delivery in NestJS?
22How do you implement event sourcing with NestJS microservices?
23How do you implement retry logic with exponential backoff for failed microservice calls in NestJS?
24How do you test a NestJS microservice controller in isolation without a real message broker?
25How do you implement service discovery and load balancing across NestJS microservice instances?
24 / 25

How do you test a NestJS microservice controller in isolation without a real message broker?

Create a TestingModule with the controller and mocked service providers. Call the handler methods directly — no NestFactory.createMicroservice(), no broker connection, and no transport is needed. The message pattern decorators are metadata only and do not affect how the method executes when called directly.

Microservice controller unit test without a broker
Microservice controller testing strategy:
  1. 1

    Call handler methods directly — @MessagePattern and @EventPattern decorators are metadata, not runtime wrappers.

  2. 2

    No broker connection is needed — the transport layer is completely irrelevant to handler logic.

  3. 3

    Mock injected services with useValue and jest.fn() — same approach as HTTP controller tests.

  4. 4

    For integration tests that verify the transport, use a test Docker Compose with a real broker.

  5. 5

    Test error paths by making mocked services throw RpcException and asserting the re-thrown exception.