NestJS NATS JetStream Transporter

A NATS transporter for NestJS that takes advantage of JetStream for event patterns.

• NestJS NATS JetStream Transporter
  • Installation
  • Publishing Messages
    • Request-Reply
    • Event-Based
  • Receiving Messages
    • Customizing JetStream consumer options
    • NACK and TERM JetStream messages
    • Queue Groups
  • Tests

Installation

1$ npm install nestjs-nats-jetstream-transporter nats@latest

Publishing Messages

The NatsClient works mostly the same with the built-in NATS transporter for NestJS. The only difference is that you must instantiate NatsClient yourself.

Request-Reply

1// main.ts
2import { NatsTransportStrategy } from "nestjs-nats-jetstream-transporter";
3
4const app = await NestFactory.createMicroservice(AppModule, {
5  strategy: new NatsTransportStrategy()
6});
7
8await app.listenAsync();

1// math.controller.ts
2import { NatsClient } from "nestjs-nats-jetstream-transporter";
3
4@Controller()
5export class MathController {
6  private readonly client = new NatsClient();
7
8  accumulate(): Observable<number> {
9    return this.client.send<number>("sum", [1, 2, 3]);
10  }
11}

Event-Based

1// main.ts
2import { NatsTransportStrategy } from "nestjs-nats-jetstream-transporter";
3
4const app = await NestFactory.createMicroservice(AppModule, {
5  strategy: new NatsTransportStrategy({
6    // Create a stream with a subject called "orders.created"
7    // This is important later on when we publish an event with NatsClient
8    streams: [
9      {
10        name: "orders-events",
11        subjects: ["orders.created"]
12      }
13    ]
14  })
15});
16
17await app.listenAsync();

1// orders.controller.ts
2import { NatsClient } from "nestjs-nats-jetstream-transporter";
3
4@Controller()
5export class OrdersController {
6  private readonly client = new NatsClient();
7
8  constructor(private readonly ordersService: OrdersService) {}
9
10  async create(): Promise<void> {
11    const order = await this.ordersService.create();
12
13    this.client.emit("orders.created", order);
14  }
15}

Receiving Messages

There are no special changes needed to receive messages. Just use the @EventPattern() and @MessagePattern() decorators provided by NestJS.

@Ctx() works exactly the same, however you should use the NatsContext provided by this package as the parameter type. It exposes an additional getMessage() method that returns the original message object if needed.

Customizing JetStream consumer options

You can customize how the JetStream push consumer behaves. One example is making the consumer durable to survive application restarts. Another example is taking advantage of distributed queues for horozontal scaling.

Read more about JetStream consumers here, and refer to the underlying API here.

1const app = await NestFactory.createMicroservice(AppModule, {
2  strategy: new NatsTransportStrategy({
3    consumer: (options) => {
4      options.durable("my-durable-name");
5      options.queue("my-queue-group");
6    }
7  })
8});

NACK and TERM JetStream messages

By default, all JetStream messages are automatically acknowledged. However, you can also NACK and TERM the message by returning the respective symbols from your application.

Returning NACK will ask for the message to be redelivered, while TERM will terminate future deliveries of the message.

1// shipping.controller.ts
2import { NACK, TERM } from "nestjs-nats-jetstream-transporter";
3
4@Controller()
5export class ShippingController {
6  constructor(private readonly shippingService: ShippingService) {}
7
8  @EventPattern("orders.created")
9  handleCreatedOrder(order) {
10    // If a shipment cannot be scheduled at this time, then ask for the message to be redelivered
11    if (this.shippingService.isBusy()) {
12      return NACK;
13    }
14
15    // If a shipment already exists for this order, then terminate the redelivery of this message
16    if (this.shippingService.exists(order)) {
17      return TERM;
18    }
19
20    this.shippingService.scheduleShipment(order);
21    
22    // Otherwise, the message will be auto-acked
23  }
24}

If the handler for your event pattern throws an error, the message will automatically be terminated. You can change this behavior by providing an onError function to the transport strategy options.

1const app = await NestFactory.createMicroservice(AppModule, {
2  strategy: new NatsTransportStrategy({
3    // Messages that caused an exception will be acked instead
4    onError: (message) => message.ack()
5  })
6});

Queue Groups

You can specify a queue group name to enable distributed queues. This will load balance message delivery across all other application instances with the same queue group name. It makes horozontal scaling simple as you can scale up by running another instance of your application with no additional configuration.

1const app = await NestFactory.createMicroservice(AppModule, {
2  strategy: new NatsTransportStrategy({
3    queue: "my-queue-group"
4  })
5});

If you want to enable this functionality for event patterns, you must also specify the queue group name using the JetStream consumer options builder.

1const app = await NestFactory.createMicroservice(AppModule, {
2  strategy: new NatsTransportStrategy({
3    consumer: (options) => options.queue("my-queue-group"),
4    queue: "my-queue-group"
5  })
6});

Tests

1$ npm run test