Why nestjs

[ElYazidDaoudi]

Hi,
First thanks for the huge work !
I'm still learning DDD

I've two questions

• Why did you choose nestjs and not doing it from scratch (using nest create a dependancy) ?
• Whats happen if an event fail ?
  For example :

async delete(entity: Aggregate): Promise<boolean> {
    entity.validate();
    const query = sql`DELETE FROM ${sql.identifier([
      this.tableName,
    ])} WHERE id = ${entity.id}`;

    this.logger.debug(
      `[${RequestContextService.getRequestId()}] deleting entities ${
        entity.id
      } from ${this.tableName}`,
    );

    const result = await this.pool.query(query);

    await entity.publishEvents(this.logger, this.eventEmitter);

    return result.rowCount > 0;
  }

Here whats happen if an error occur on the publishEvents or on one of the emitted event ? the query will not be committed ?
And with the last version the event was executed after the commit and now is executed before the commit why ?

THanks a lot

[Sairyss]

1. I chose NestJS because it gives you an easy way to do repetitive stuff. For example to create a new endpoint you just need a few decorators, like @Controller or @Post/@Get/@Delete, dependency injection is easy with @Inject decorator, etc. Doing it from scratch would take a lot of work, and in the end you would end up re-implementing your own framework anyway. So it's better to just use an existing battle-tested framework rather than reinvent the wheel.
2. If transaction is started, on event failure everything will be rolled back.

[ElYazidDaoudi]

thanks dude