Apa perbedaan antara embedding dan referencing?

Question

Accepted Answer

**Embedding** nyimpen data sing ana gandhengane *ing dalam* dokumen (nested); **referencing** nyimpen ing dokumen sing *kapisah-pisah* sing disambung dening id. Iki minangka keputusan modeling inti ing MongoDB, kanthi trade-off sing beda-beda kanggo performa baca, ukuran data, lan kompleksitas update.

## Embedding — nested ing dalam dokumen

```js
{
  _id: ObjectId("..."),
  title: "My Post",
  author: { name: "Ann", email: "ann@x.com" },   // EMBEDDED author
  comments: [                                      // EMBEDDED comments
    { user: "Bob", text: "Great!" },
    { user: "Carol", text: "Thanks" }
  ]
}
// ✓ ONE query gets the post + author + comments (fast, atomic)
// ✗ if author info changes, must update it in every post embedding it (duplication)
// ✗ document grows with comments → could hit the 16MB limit if unbounded
```

## Referencing — dokumen kapisah-pisah sing disambung dening id

```js
// posts collection
{ _id: ObjectId("p1"), title: "My Post", authorId: ObjectId("u1") }
// users collection
{ _id: ObjectId("u1"), name: "Ann", email: "ann@x.com" }
// comments collection
{ _id: ObjectId("c1"), postId: ObjectId("p1"), user: "Bob", text: "Great!" }

// ✓ author/comments stored ONCE, updated in one place; no document-size issues
// ✓ each entity managed independently
// ✗ need multiple queries or $lookup to combine (slower reads for related data)
```

## Trade-off ing jejere

```text
                  Embedding                    Referencing
Reads             ✓ fast (one query)           ✗ multiple queries / $lookup
Data duplication  ✗ duplicated (update many)   ✓ stored once
Document size     ✗ grows (16MB limit risk)    ✓ no size concern
Updates           ✗ update in every copy       ✓ update in one place
Atomicity         ✓ atomic (single document)   ✗ across documents
Best for          contains, accessed-together  shared, large, independent, many
```

## Pendekatan hybrid (umum)

```js
// embed a SUBSET for fast reads, reference for the full data
{ title: "Post", author: { _id: ObjectId("u1"), name: "Ann" } }  // enough for display
// → reference (author._id) for full details when needed; embed name for the common read
```

## Mengapa iki penting

Pamahaman tentang embedding vs referencing minangka **keahlian inti MongoDB data modeling**, dadi pengetahuan essential kanggo ndesain aplikasi MongoDB sing efektif.

Keputusan iki — nyimpen data sing ana gandhengane ing dalam dokumen (embedding) versus ing dokumen kapisah-pisah sing disambung (referencing) — langsung nentokake performa baca aplikasi, konsistensi data, ukuran dokumen, lan kompleksitas update, dadi pilihan desain MongoDB sing paling besar pengaruhe.

Pamahaman tentang **trade-off** minangka kunci: **embedding** menehi baca query-siji sing cepet saka data sing ana gandhengane lan update atomik (cocok kanggo relasi "contains", data sing diakses bareng-bareng, sub-data sing kebatas) nanging nyebabake duplikasi (kompleksitas update yen data dibagi) lan pertumbuhan dokumen (resiko melampaui batas 16MB yen unbounded); **referencing** nyimpen data sekali (update gampang, ora ana duplikasi, ora ana masalah ukuran, manajemen mandiri) nanging mbutuhake query multiple atau `$lookup` kanggo nggabung (baca data gandhengane sing luwih pelan).

Ngerteni apa sing cocok scenario endi — embed kanggo data kebatas, milik, diakses bareng-bareng; reference kanggo data gedhe, dibagi, mandiri, utawa relasi akeh — minangka pertimbangan modeling sing essential.

Pamahaman tentang **pendekatan hybrid** umum (embedding subset kanggo baca cepet sambil referencing kanggo data lengkap — nggoleki sing paling apik) nggambarake desain sing canggih.

Awit keputusan iki nduweni pengaruh jero ning kualitas aplikasi MongoDB (pilihan salah nyebabake query pelan, dokumen gedhe, utawa update sing nyusahaké), lan awit iki keahlian modeling fundamental, khas MongoDB (ora ana equivalent langsung SQL — SQL normalize kanthi default), pamahaman embedding vs referencing — trade-off, kapan nggunakake saben, lan pendekatan hybrid — minangka pengetahuan essential, nilaiyen-tinggi sing ana ing jantung modeling data MongoDB sing efektif lan salah siji topik MongoDB paling penting lan akeh dibahas, central kanggo ndesain schema sing perform apik kanggo pola akses aplikasi.