X'inhu l-lifecycle hooks li NestJS jipprovdi?

Question

Accepted Answer

NestJS jipprovdi **lifecycle hooks** — metodi li timplemenntahom biex tħaddem code f'mumenti speċifiċi fil-ċiklu tal-ħajja tal-applikazzjoni jew ta' provider (inizjalizzazzjoni u shutdown). Huma essenzjali għall-setup (konnessjoni ma' risorsi) u cleanup (għeluq konnessjonijiet b'mod kordin).

## Il-ħuks prinċipali

```ts
@Injectable()
export class DatabaseService
  implements OnModuleInit, OnApplicationShutdown {

async onModuleInit() {
    // runs once the host MODULE's dependencies are resolved → do INITIALIZATION
    await this.connect();         // e.g. open a database connection
  }

async onApplicationShutdown(signal: string) {
    // runs when the app is shutting down → do CLEANUP
    await this.disconnect();      // close connections, flush, release resources
  }
}
```

## Is-sekwenza tal-ħajja

```text
INITIALIZATION (startup):
  onModuleInit()          → after the module's providers are initialized
  onApplicationBootstrap()→ after ALL modules are initialized (whole app ready)

SHUTDOWN (graceful termination):
  onModuleDestroy()         → cleanup as modules are destroyed
  beforeApplicationShutdown() → before shutdown completes
  onApplicationShutdown(signal) → final shutdown (signal = SIGTERM, etc.)
```

## Użu komuni: servizz Prisma konness/diskonness

```ts
@Injectable()
export class PrismaService extends PrismaClient
  implements OnModuleInit, OnModuleDestroy {

async onModuleInit() {
    await this.$connect();        // connect on startup
  }
  async onModuleDestroy() {
    await this.$disconnect();      // disconnect on shutdown — clean release
  }
}
```

Din hija l-mudell standard għal risorsi li jeħtieġu setup/teardown esplisitu — konnetti f' `onModuleInit`, ħeluq f' `onModuleDestroy`.

## Tħattir il-shutdown hooks

```ts
// shutdown hooks must be enabled explicitly
const app = await NestFactory.create(AppModule);
app.enableShutdownHooks();        // ❗ required for onApplicationShutdown etc. to fire
```

Il-shutdown hooks jiddu biss jekk tħaddem `enableShutdownHooks()` — faċli li tinsa, imbagħad il-cleanup qatt ma jiħdux.

## Għaliex graceful shutdown għandu importanza

```text
When the app receives SIGTERM (deploy, scale-down, container stop):
  ✗ Without shutdown hooks → connections left open, in-flight work dropped
  ✓ With shutdown hooks → close DB/Redis/queues cleanly, finish work → zero-downtime
```

## Għaliex qawwalu importanti

Il-lifecycle hooks huma importanti biex timmaniġġja r-risorsi b'mod korrett f'applikazzjonijiet NestJS — jipprovdu l-postijiet xierqa biex twettaq **inizjalizzazzjoni** (ftuħ konnessjonijiet database/Redis, tagħbija tal-data, reġistrazzjoni ma' servizzi) u, kritikament, **cleanup bil-grazzja** fuq shutdown (għeluq konnessjonijiet, flushing tal-buffers, tmiem tal-ħiduma li għaddejja).
")[Fehim tagħhom hu essenzjali għal affidabbiltà fl-produzzjoni: il-**hooks ta' inizjalizzazzjoni** (`onModuleInit`, `onApplicationBootstrap`) jiżguraw li setup jiġri fil-ħin xieraq ladarba d-dipendenzi huma lesti, u l-**shutdown hooks** (`onModuleDestroy`, `onApplicationShutdown`) jippermettulna **graceful shutdown** — li hu vitali f'deployment modern (kontajners/orkestraturi jibagħtu SIGTERM kontinwament waqt deploys u scaling, u mingħajr cleanup xieraq tixrax konnessjonijiet u titbatt requests attivi, tqassar zero-downtime deployments).

Il-mudell standard ta' konnessjoni f' `onModuleInit` u diskonness f' `onModuleDestroy` (p.ex. għal servizzi Prisma/database) hu għarif ta' kuljum NestJS, u jaf ir-rekwiżit sottilja li ħtieġ tħaddem `enableShutdownHooks()` (jew shutdown hooks səlilentement qatt ma jiddu) hu dettall prattiku, faċli li jinsa.

Master tal-lifecycle hooks hu parti ta' bini ta' servizzi NestJS robusti u pronti għall-produzzjoni li jimmanipulaw r-risorsi u d-deployments b'mod korrett.