event-listeners

name	event-listeners
description	Use when creating event listeners that react to domain events — same-BC side effects (projections, audit, cache), cross-BC reactions (another bounded context consuming events), or bridge listeners (WebSocket broadcast, RabbitMQ publish, email). Covers listener taxonomy, placement rules, Strategy+Gateway pattern for fan-out, and anti-over-engineering criteria.
argument-hint	Event and type (e.g., "OrderCreatedEvent broadcast", "cross-bc OrderPaid", "projection Order")

Event Listeners

Domain events emitted via entity.commit() flow through the NestJS CQRS EventBus. Listeners are @EventsHandler classes that react to these events. Multiple handlers for the same event run in parallel via Promise.allSettled — if one fails, others continue.

This skill covers WHERE listeners live, WHAT they do, and WHEN you actually need one.

---

Decision Tree

Do you need to react to a domain event?
│
├─ Is it a side effect within the SAME bounded context?
│  └─ YES → Same-BC Listener (see Section 1)
│     Examples: update Redis projection, write audit log, invalidate cache
│
├─ Does ANOTHER bounded context need to react?
│  └─ YES → Cross-BC Listener (see Section 2)
│     Examples: Billing creates invoice when Order is created
│
├─ Does the event need to leave the process?
│  └─ YES → Bridge Listener (see Section 3)
│     Examples: WebSocket broadcast, RabbitMQ publish, send email, call webhook
│
└─ Is the side effect simple and only 1 consumer exists?
   └─ YES → Consider putting it in the command handler directly (no listener needed)

---

When NOT to Create a Listener (anti-over-engineering)

Situation	Do this instead
Only 1 side effect, simple and synchronous	Put it in the command handler after entity.commit()
Side effect is part of the core business transaction	Keep it in the use case / handler — not a separate listener
< 2 consumers for the event	Question whether you need the event at all
Event payload identical to what listener would emit	Emit directly from handler, skip intermediate event

Principle: Events are for decoupling. If there's nothing to decouple, don't add the indirection.

---

Section 1: Same-BC Listener

Lives in <bc>/infrastructure/listeners/. Reacts to events from its OWN bounded context.

// infrastructure/listeners/order-created-projection.handler.ts
import { EventsHandler, IEventHandler } from '@nestjs/cqrs';
import { Inject, Logger } from '@nestjs/common';

import { OrderCreatedEvent } from '../../domain/events/order-created.event';
import { REDIS_READ_MODEL_TOKEN } from '../../application/ports/read-model.port';
import type { ReadModelPort } from '../../application/ports/read-model.port';

@EventsHandler(OrderCreatedEvent)
export class OrderCreatedProjectionHandler implements IEventHandler<OrderCreatedEvent> {
  private readonly logger = new Logger(OrderCreatedProjectionHandler.name);

  constructor(
    @Inject(REDIS_READ_MODEL_TOKEN)
    private readonly readModel: ReadModelPort,
  ) {}

  async handle(event: OrderCreatedEvent): <> {
     {
       ..(, {
        : event.,
        : event.,
        : event.,
        : event.,
        : event..(),
      });
    }  (error) {
      
      ..(, error);
    }
  }
}

Common same-BC listeners:

• Projection updater — writes denormalized view to Redis/MongoDB
• Audit log — records domain change for compliance
• Cache invalidation — clears stale cache entries
• Counter update — increments/decrements aggregate counters

See references/same-bc-listeners.md for full templates.

---

Section 2: Cross-BC Listener

Cross-BC communication uses the Integration Event Port pattern with an Anti-Corruption Layer (ACL):

• Domain Event = INTERNAL to the BC. Never leaves the bounded context.
• Integration Event = PUBLIC contract between BCs. Always via port/adapter.
• ACL = Adapter in the consuming BC that translates external model to internal model.

The 3-part flow:

OrderBC (emitter)                      InvoicingBC (consumer)
  domain/events/order-paid.event.ts
  application/ports/
    order-integration-events.port.ts  ←  implemented by →  InvoiceIntegrationAdapter
  infrastructure/listeners/
    order-paid-integration.handler.ts                         ↓ dispatches CreateInvoiceCommand

Part 1 — Port definition (in emitting BC):

// orders/application/ports/order-integration-events.port.ts
export const ORDER_INTEGRATION_EVENTS_TOKEN = Symbol('OrderIntegrationEvents');

export interface OrderIntegrationEventsPort {
  orderPaid(payload: {
    orderId: string;
    organizationId: string;
    customerId: string;
    total: number;
    currency: string;
  }): Promise<void>;
}

Part 2 — Publisher handler (in emitting BC):

// orders/infrastructure/listeners/order-paid-integration.handler.ts
import { EventsHandler, IEventHandler } from '@nestjs/cqrs';
import { Inject, Logger } from '@nestjs/common';
import { OrderPaidEvent } from '../../domain/events/order-paid.event';
import {
  ORDER_INTEGRATION_EVENTS_TOKEN,
  type OrderIntegrationEventsPort,
} from '../../application/ports/order-integration-events.port';

@EventsHandler(OrderPaidEvent)
export class OrderPaidIntegrationHandler implements IEventHandler<OrderPaidEvent> {
  private readonly logger = new Logger(OrderPaidIntegrationHandler.name);

  constructor(
    @Inject(ORDER_INTEGRATION_EVENTS_TOKEN)
    private readonly integrationEvents: OrderIntegrationEventsPort,
  ) {}

  async handle(event: OrderPaidEvent): Promise<void> {
     {
       ..({
        : event.,
        : event.,
        : event.,
        : event.,
        : event.,
      });
    }  (error) {
      ..(
        ,
        error   ? error. : (error),
      );
    }
  }
}

Part 3 — Consumer adapter (ACL in consuming BC):

// invoicing/infrastructure/adapters/order-integration-events.adapter.ts
import { Injectable } from '@nestjs/common';
import { CommandBus } from '@nestjs/cqrs';
import { type OrderIntegrationEventsPort } from '@/enterprise/orders/application/ports/order-integration-events.port';
import { CreateInvoiceCommand } from '../../application/commands/create-invoice.command';

@Injectable()
export class OrderIntegrationEventsAdapter implements OrderIntegrationEventsPort {
  constructor(private readonly commandBus: CommandBus) {}

  async orderPaid(payload: {
    orderId: string;
    organizationId: string;
    customerId: string;
    total: number;
    currency: string;
  }): Promise<void> {
    // ACL: translate Orders BC model to Invoicing BC model
    await this.commandBus.(
       (
        payload.,
        payload.,
        payload.,
        payload.,
        payload.,
      ),
    );
  }
}

Module wiring — emitter BC provides the token:

// orders/orders.module.ts
{
  provide: ORDER_INTEGRATION_EVENTS_TOKEN,
  useClass: OrderIntegrationEventsAdapter,  // wired from InvoicingModule via DI
}

Key rules:

1. Orders BC NEVER imports from Invoicing BC
2. Invoicing BC implements the port that Orders BC defines
3. The ACL adapter is the only place that knows both models
4. try/catch mandatory in the publisher handler — cross-BC failure must not affect emitting BC

3 approaches — choose by deployment context:

Approach	When to use
Integration Event Port (this pattern)	Modular monolith — recommended
String events via EventEmitter2	Simpler, but loses type-safety
Message broker (RabbitMQ/Kafka)	Microservices — maximum decoupling

See references/cross-bc-listeners.md for full templates and testing patterns.

---

Section 3: Bridge Listener

Transforms a domain event into an external output: WebSocket broadcast, RabbitMQ message, email, webhook.

// infrastructure/listeners/order-created-broadcast.handler.ts
import { EventsHandler, IEventHandler } from '@nestjs/cqrs';
import { Inject, Logger } from '@nestjs/common';

import { OrderCreatedEvent } from '../../domain/events/order-created.event';
import { WS_GATEWAY_TOKEN, type WsGatewayPort } from '@/shared/ports/ws-gateway.port';

@EventsHandler(OrderCreatedEvent)
export class OrderCreatedBroadcastHandler implements IEventHandler<OrderCreatedEvent> {
  private readonly logger = new Logger(OrderCreatedBroadcastHandler.name);

  constructor(
    @Inject(WS_GATEWAY_TOKEN) private readonly gateway: WsGatewayPort,
  ) {}

  async handle(event: OrderCreatedEvent): Promise<void> {
    try {
      this..(event., , {
        : event.,
        : event.,
        : event.,
      });
    }  (error) {
      ..(, error);
    }
  }
}

Bridge types:

• WebSocket — WsGatewayPort.emitToOrganization() (see websocket-broadcasting skill)
• Message broker — publish to RabbitMQ/Kafka exchange for microsservice consumption
• Email — send via EmailPort (notification listeners)
• Webhook — POST to external URL via HttpPort

See references/bridge-listeners.md for full templates.

---

Strategy + Gateway Pattern (3+ consumers)

When 3+ listeners react to the same event and share pre-processing (validation, enrichment), use the Gateway pattern with Strategy fan-out.

When to use: 3+ consumers for the same event that share common logic. When NOT to use: < 3 consumers — separate handlers are simpler.

// Interface for listener strategies
export interface EventListenerStrategy<T> {
  supports(event: T): boolean;
  execute(event: T): Promise<void>;
}

// Gateway handler — single @EventsHandler, fans out to strategies
@EventsHandler(OrderCreatedEvent)
export class OrderCreatedGateway implements IEventHandler<OrderCreatedEvent> {
  private readonly logger = new Logger(OrderCreatedGateway.name);

  constructor(
    @Inject('ORDER_CREATED_STRATEGIES')
    private readonly strategies: EventListenerStrategy<OrderCreatedEvent>[],
  ) {}

  async handle(event: OrderCreatedEvent): Promise<void> {
    const applicable = this.strategies.filter(s => s.supports(event));

    const results = await .(
      applicable.( strategy.(event)),
    );

     ( result  results) {
       (result. === ) {
        ..(, result.);
      }
    }
  }
}


()
    <> {
  ():  {  ; }
   (: ): <> {  }
}

()
    <> {
  ():  {  ; }
   (: ): <> {  }
}

()
    <> {
  (: ):  {
     event. > ;  
  }
   (: ): <> {  }
}


{
  : ,
  : (
    : ,
    : ,
    : ,
  ): <>[] => [projection, broadcast, invoice],
  : [, , ],
}

Benefits over separate handlers:

• Centralized error isolation (Promise.allSettled)
• Shared pre-processing (fetch once, pass to all)
• Dynamic enable/disable via supports()
• Single @EventsHandler registration per event

Trade-off: More indirection. Only use when the benefits outweigh the simplicity of separate handlers.

---

Listener Registration

All listeners are registered in the CONSUMING module's providers array:

// In the module that CONSUMES the event
@Module({
  imports: [CqrsModule],
  providers: [
    // Same-BC listeners
    OrderCreatedProjectionHandler,
    OrderUpdatedCacheInvalidator,

    // Cross-BC listeners (events imported from other BCs)
    PaymentReceivedInvoiceHandler,

    // Bridge listeners
    OrderCreatedBroadcastHandler,

    // Strategy gateway (if using Strategy pattern)
    OrderCreatedGateway,
    OrderProjectionStrategy,
    OrderBroadcastStrategy,
    OrderInvoiceStrategy,
    {
      provide: 'ORDER_CREATED_STRATEGIES',
      useFactory: (...strategies) => strategies,
      inject: [OrderProjectionStrategy, OrderBroadcastStrategy, OrderInvoiceStrategy],
    },
  ],
})
export class OrdersModule {}

---

Testing Listeners

describe('OrderCreatedProjectionHandler', () => {
  let handler: OrderCreatedProjectionHandler;
  let readModel: MockReadModelPort;

  beforeEach(() => {
    readModel = { upsert: vi.fn(), get: vi.fn(), delete: vi.fn() };
    handler = new OrderCreatedProjectionHandler(readModel);
  });

  it('should update read model on order created', async () => {
    const event = new OrderCreatedEvent('order-1', 'org-1', 1000, 'PENDING');

    await handler.handle(event);

    expect(readModel.upsert).toHaveBeenCalledWith('order:order-1', {
      id: 'order-1',
      total: 1000,
      status: 'PENDING',
      organizationId: 'org-1',
      updatedAt: expect.any(String),
    });
  });

  it('should not throw on read model failure', async () => {
    readModel..( ());
     event =  (, , , );

    
     (handler.(event))..();
  });
});

---

References

File	Content
references/same-bc-listeners.md	Projection updater, audit log, cache invalidation, counter update
references/cross-bc-listeners.md	Event import rules, CommandBus dispatch, module wiring, circular dep avoidance
references/bridge-listeners.md	WS broadcast, RabbitMQ publish, email notification, webhook POST