NestJS library solves dual-write problem using transactional outbox and idempotent inbox

A common bug in event-driven backends occurs when a process crashes after writing to a database but before publishing a broker event, causing silent data inconsistencies — a problem known as dual-write. The proven fix is the transactional outbox pattern, which writes both the business record and the event to the same database transaction, then uses a background worker to relay committed events to the broker. To handle duplicate deliveries, the consumer side uses an idempotent inbox that ensures each event is processed exactly once. A new open-source library, @nest-native/messaging, implements both patterns for the NestJS framework using Drizzle ORM, filling a gap left by existing libraries that only support TypeORM and MikroORM. The library supports SQLite, Postgres, and MySQL dialects and integrates with standard NestJS dependency injection and transactional decorators.