Pawak replikasi tindak-tanduk ing PostgreSQL?

Question

Accepted Answer

**Replikasi** nggawe salinan data saka basis data **primary** menyang siji utawa luwih **replica** (standby) servers — kanggo high availability (failover yen primary gagal) lan read scaling (menyebarake query baca). PostgreSQL utamane nggunakake **streaming replication** (physical) adhedhasar write-ahead log (WAL).

## Streaming (physical) replication

```text
Primary  ──(streams WAL: the write-ahead log of changes)──▶  Replica(s)
  ✓ The primary handles all WRITES
  ✓ Replicas continuously apply the primary's WAL → stay in sync (near-real-time)
  ✓ Replicas can serve READ queries ("hot standby") → scale reads
```

Primary ngirim **WAL** (write-ahead log — rekaman saben owah-owahan) menyang replika, kang ngetrapake supaya tetep selaras. Replika dadi salinan sing mung bisa maca sing bisa nglayani query baca.

## Kauntungan: HA lan read scaling

```text
HIGH AVAILABILITY → if the primary fails, a replica can be PROMOTED to primary (failover)
  → minimal downtime, no data loss (with synchronous replication)
READ SCALING → route read-only queries to replicas → offload the primary
  → handle more read traffic (great for read-heavy workloads)
BACKUPS → take backups from a replica without loading the primary
```

## Sinkron versus asinkron replikasi

```text
ASYNCHRONOUS (default) → the primary commits without waiting for replicas
  ✓ faster writes (no wait)   ✗ a tiny window of potential data loss on failover
SYNCHRONOUS → the primary waits for a replica to confirm before committing
  ✓ no data loss on failover  ✗ slower writes (waits for the replica)
→ Choose based on the durability vs performance trade-off.
```

## Logical replication (model beda)

```text
LOGICAL replication → replicates specific TABLES/changes (not the whole cluster), based
on a publish/subscribe model. Enables: selective replication, cross-version, and
replicating to different schemas → good for migrations, integrations, partial replication.
```

## High availability ing praktik

```text
Tools like Patroni, repmgr, or cloud-managed Postgres automate FAILOVER (detecting
primary failure and promoting a replica) → near-automatic high availability.
A load balancer / connection router directs writes to the primary, reads to replicas.
```

## Napa iki penting

Replikasi penting kanggo mbangun PostgreSQL deployment kang **highly-available lan scalable**, mula mangerteni iki karuwan pikenan senior-level kanggo arsitektur basis data produksi.

Rong kauntungan inti penting kanggo aplikasi serius: **high availability** (yen basis data primary gagal, replica bisa dipromosi kanggo njegok, nyilikke downtime — penting kanggo sistem kang kudu tetep ana) lan **read scaling** (rutinisasi query mung baca menyang replika ndhelikake primary, nglilani sistem nangani traffic baca luwih akeh — mahal kanggo workload sing akeh maca).

Mangerteni **streaming replication** (primary ngirim WAL-ne menyang replika kang tetep selaras lan bisa nglayani baca) dadi fondasi.

Tabu **synchronous versus asynchronous** trade-off penting: asinkron (default — nyerat luwih cepet nanging jendhela cilik kemungkinan ilang data sawise failover) laban sinkron (ora ilang data nanging nyerat luwih alon) — keputusan durability-versus-performance kang anggo keandalan.

Mangerteni **logical replication** (ngreplika tabel khusus via pub/sub, migunani kanggo migrasi, cross-version, lan replikasi parsial/selektif) ngebentuk pilihan.

Tabu **HA tooling** (Patroni, repmgr, managed cloud Postgres) ngatomatisake failover, lan routing read/write nggiraa traffic kanthi laras, karuwan pengetahuan arsitektur praktis.

Amarga high availability lan scalability karuwan requirement penting kanggo sistem basis data produksi, lan amarga replikasi (kanthi HA failover, read scaling, sync/async durability trade-off, lan logical replication kanggo fleksibilitas) dadi mekanisme utama kang PostgreSQL tawarake, mangerteni replikasi karuwan pikenan senior-level penting kanggo arsitektur Postgres deployment kang andal lan scalable — prihatin kang sering relevan kanggo sistem produksi lan topik kang nuduhake pamahaman basis data availability lan scaling kang dikarepake kanggo senior database/backend roles.