Kif tiddisinja skemi fil-MongoDB?

Question

Accepted Answer

Il-MongoDB schema design isentru fuq deċiżjoni ewlenija: **embedding** (ħżin ta' data relatata ġewwa dokument) versus **referencing** (ħżin ta' data relatata f'dokumenti/kollezzjonijiet separati b'referenzi). Bħala differenza mill-approċċ default ta' SQL li jinormalizza, id-disinn ta' MongoDB jottimizza kif id-data hija *aċċessata*.

## Embedding — ħżin ta' data relatata flimkien

```js
// embed related data within the document
{
  _id: ObjectId("..."),
  name: "Ann",
  address: { city: "NY", zip: "10001" },        // embedded sub-document
  orders: [                                      // embedded array of orders
    { product: "Phone", amount: 999 },
    { product: "Case", amount: 20 }
  ]
}
// → ONE query gets the user AND their address AND orders (no joins)
```

**Embedding** iżomm data relatata f'dokument wieħed — aqraha kollha f'query wieħed (veloċe, ebda joins). Tajjeb għal data aċċessata flimkien u relazzjonijiet ta' "contains".

## Referencing — link ta' dokumenti separati

```js
// store a reference (id) to a document in another collection
{ _id: ObjectId("u1"), name: "Ann" }                          // users collection
{ _id: ObjectId("o1"), userId: ObjectId("u1"), product: "Phone" } // orders collection
// → query orders by userId; use $lookup to join when needed
```

**Referencing** iħżen data separatament u jkollegha bl-id (bħal foreign key) — query separatament jew join b' `$lookup`.

## Meta embed versus reference

```text
EMBED when:
  ✓ data is accessed TOGETHER (read the parent → you want the children)
  ✓ a "contains"/ownership relationship (address, order line items)
  ✓ the embedded data is bounded (not unboundedly growing)
  ✓ one-to-few relationships

REFERENCE when:
  ✓ data is large or grows UNBOUNDEDLY (avoid huge documents — 16MB doc limit!)
  ✓ data is accessed/updated INDEPENDENTLY
  ✓ many-to-many or one-to-many with many
  ✓ the same data is shared/referenced by many documents (avoid duplication)
```

## Disinn għal access patterns (il-prinċipju ewleniju)

```text
MongoDB schema design is driven by HOW YOU QUERY the data, not pure normalization:
  → Structure data so common queries are efficient (often a single document read).
  → "Data that is accessed together should be stored together."
  → This may mean DENORMALIZING (some duplication) for read efficiency — acceptable
    in MongoDB, traded against update complexity.
```

## Għaliex ikun importanti

Id-disinn tal-skemi huwa kritikament importanti fil-MongoDB — inhu differenti minn u possibbilment aktar konsekwenzjali milli fil-SQL, għaliex il-mudell flessibbli tal-dokumenti ta' MongoDB jagħtik għażliet li jaffettwaw b'mod sinifikanti l-performance u l-maintainability, għalhekk il-fehim tiegħu hu essenzjali għall-bini ta' applikazzjonijiet MongoDB effettivi.
"}}