Kepiye cara transaksi ngojog ing MongoDB?

Question

Accepted Answer

MongoDB ndhukung **transaksi ACID multi-dokumen** (wiwit v4.0 kanggo replica sets, v4.2 kanggo sharded clusters) — nggelumpukake operasi ing sawetara dokumen/koleksi supaya kabeh bisa kasil utawa kabeh bisa gagal. Nanging, model dokumen MongoDB asring nggawe transaksi *ora perlu* liwat operasi atomic single-dokumen.

## Operasi single-dokumen wis atomic

```text
KEY POINT: operations on a SINGLE document are ALWAYS atomic in MongoDB.
→ Because related data is often EMBEDDED in one document, many operations that would
  need a transaction in SQL are a single atomic document update in MongoDB.
→ Good schema design (embedding) often eliminates the NEED for multi-doc transactions.
```

```js
// updating a document and its embedded array atomically — NO transaction needed
db.accounts.updateOne(
  { _id: id },
  { $inc: { balance: -100 }, $push: { transactions: { amount: -100 } } }
);  // atomic — both changes succeed or fail together (single document)
```

## Transaksi multi-dokumen (yen bener-bener dibutuhake)

```js
// for operations across MULTIPLE documents/collections that must be atomic
const session = db.getMongo().startSession();
session.startTransaction();
try {
  db.accounts.updateOne({ _id: 1 }, { $inc: { balance: -100 } }, { session });
  db.accounts.updateOne({ _id: 2 }, { $inc: { balance: 100 } }, { session });
  session.commitTransaction();        // both succeed together
} catch (e) {
  session.abortTransaction();          // or both roll back
} finally {
  session.endSession();
}
```

Transaksi multi-dokumen (nganggo session) menehi jaminan ACID ing seluruh dokumen — kanggo kasus kaya nransfer antarane dokumen akun kapisah.

## Nggunakake transaksi kanthi irit

```text
✓ Transactions are available and provide ACID across documents WHEN NEEDED
✗ But they have PERFORMANCE COSTS (overhead, locking) — don't overuse them
→ PREFER good schema design (embedding related data) so single-document atomic
  operations suffice. Use multi-document transactions only when data genuinely
  spans documents and must be consistent (e.g. money transfers between accounts).
→ Requires a replica set (not standalone).
```

## Napa iki penting

Paham transaksi MongoDB — lan sing penting, kapan wae perlu — penting kanggo njamin konsistensi data ing aplikasi MongoDB, dadi pengetahuan sing manahe kanggo membangun sistem sing bener.

Insight paling penting yaiku **operasi single-dokumen tansaya atomic** ing MongoDB, lan amarga model dokumen MongoDB nyorong **embedding data sing ana hubungane ing siji dokumen**, akeh operasi sing bakal butuh transaksi ing database relasional (ing ngendi data sing ana hubungane bisa misah ing tabel) yaiku **update dokumen atomic tunggal** ing MongoDB — dadi **desain skema sing apik asring ngilangi perlu transaksi multi-dokumen**.

Iki titik konsep kunci: atomicity-per-dokumen MongoDB, digabung karo embedding, nangani akeh kabutuhan konsistensi tanpa transaksi.

Paham yen MongoDB **ndhukung transaksi ACID multi-dokumen** (wiwit v4.0+) kanggo kasus ngendi operasi bener-bener manyebar ing sawetara dokumen/koleksi (kaya nransfer antarane dokumen akun kapisah) iku penting — ana yen bener-bener dibutuhake, menehi jaminan all-or-nothing.

Sama pentinge yaiku tuntunan kanggo **nggunakake transaksi kanthi irit**: cangkeme ana biaya kinerja (overhead, locking), dadi cara sing luwih dipilih yaiku desain skema sing apik (embedding) supaya operasi atomic single-dokumen cukup, nyisihake transaksi multi-dokumen kanggo kabutuhan konsistensi lintas dokumen sing bener.

Paham iki — atomicity single-dokumen, embedding asring ngilangi perlu transaksi, transaksi multi-dokumen ana kanggo yen bener-bener dibutuhake, lan preferensi kanggo desain liwat transaksi — ngenggamake pertimbangan MongoDB sing apik.

Amarga konsistensi data kritis lan pendekatan MongoDB (atomicity dokumen + transaksi pilihan) beda karo model transaction-centric SQL, paham transaksi MongoDB — utamane yen operasi single-dokumen atomic, embedding nyurangi kabutuhan transaksi, lan transaksi multi-dokumen ana nanging kudu digunakake kanthi bijak — yaiku pengetahuan sing berharga, penting kanggo njamin konsistensi kanthi bener lan efisien ing aplikasi MongoDB, topik sing nunjukake pemahaman babagan model konsistensi MongoDB lan praktek desain sing apik.