How do you implement idempotent event handlers to safely handle duplicate message delivery in NestJS?

Q: How do you implement idempotent event handlers to safely handle duplicate message delivery in NestJS?

// Deduplication table @Entity('processed_events') export class ProcessedEvent { @PrimaryColumn() eventId: string; @Column() processedAt: Date; } @Injectable() export class IdempotentEventHandler { async handleOnce( eventId: string, handler: () => Promise , ): Promise { await this.dataSource.transaction(async manager => { const inserted = await manager .createQueryBuilder() .insert() .into(ProcessedEvent) .values({ eventId, processedAt: new Date() }) .orIgnore() // skip insert if eventId already exists .execute(); if (inserted.raw.affectedRows === 0) { return; // duplicate — skip silently } await handler(); // execute exactly once }); } } // Usage @EventPattern('order_placed') async handleOrderPlaced(@Payload() event: OrderPlacedEvent): Promise { await this.idempotentHandler.handleOnce(event.eventId, async () => { await this.inventoryService.reserveItems(event.orderId); }); } Every event must carry a unique eventId — generate a UUID on the producer side before publishing. The deduplication insert and the handler run in the same database transaction — atomic together. orIgnore() (or ON CONFLICT DO NOTHING in SQL) makes the insert a no-op for duplicate event IDs. Clean up old processed events periodically — retain them only long enough to cover maximum redelivery windows. Idempotency is essential for Kafka (at-least-once), RabbitMQ with requeuing, and any retry mechanism.

Difficulty: 6/10

idempotency, event handling, NestJS

Store processed event IDs in a deduplification table. Use a database transaction to atomically attempt inserting the event ID and execute the handler — if the insert is skipped due to a duplicate key, the handler is not called. This ensures each event is processed exactly once even with at-least-once delivery semantics.

Idempotency via deduplication table

Idempotency implementation rules:

1
Every event must carry a unique eventId — generate a UUID on the producer side before publishing.
2
The deduplication insert and the handler run in the same database transaction — atomic together.
3
orIgnore() (or ON CONFLICT DO NOTHING in SQL) makes the insert a no-op for duplicate event IDs.
4
Clean up old processed events periodically — retain them only long enough to cover maximum redelivery windows.
5
Idempotency is essential for Kafka (at-least-once), RabbitMQ with requeuing, and any retry mechanism.

Scenario Questions

0-2 years experience

2-5 years experience

How do you implement idempotent event handlers to safely handle duplicate message delivery in NestJS?

Scenario Questions

Follow-up Questions