பிரতिलிपि (Replication) எவ்வாறு செயல்படுகிறது மற்றும் அதன் வ்யூహங்கள் என்ன?

Question

Accepted Answer

**பிரதिलिपि (Replication)** பல சர்வரங்களில் தரவின் நகलை பராமரிக்கிறது — **उपलब्धता** (failures இலிருந்து உயிர் பிழைப்பதற்கு), **read scaling** (நகलுகளிலிருந்து reads வழங்குவதற்கு), மற்றும் **புவியியல் விநியோகம் (geographic distribution)** (multiple servers முழுவதும் தரவிலிருந்து). வெவ்வேறு வ்யூહங்கள் (primary-replica, multi-primary, sync vs async) trade-offs ஐ உள்ளடக்குகின்றன.

## பிரதிலிபி செய்யவேண்டிய காரணம்

```text
✓ AVAILABILITY/redundancy → if one copy fails, others have the data (no data loss, failover)
✓ READ SCALING → serve reads from replicas (offload the primary) → handle more reads
✓ GEO-DISTRIBUTION → copies near users (lower latency); disaster recovery
→ replication is fundamental to reliable, scalable data systems.
```

## பிரதிलिपि வ්යూහங்கள்

```text
PRIMARY-REPLICA (master-slave) → one PRIMARY handles writes, replicates to READ replicas:
  ✓ simple; great for read-heavy workloads; the common model
  ✗ the primary is a write bottleneck / single point for writes (failover needed)
MULTI-PRIMARY (multi-master) → multiple nodes accept writes:
  ✓ write availability/scaling, geo-writes  ✗ CONFLICT resolution (concurrent writes to
    the same data) → complex
```

## Synchronous vs asynchronous

```text
SYNCHRONOUS → wait for replicas to confirm before acknowledging the write:
  ✓ replicas are consistent (no data loss on failover)  ✗ slower (waits); availability impact
ASYNCHRONOUS → acknowledge the write immediately; replicate in the background:
  ✓ fast writes, high availability  ✗ REPLICATION LAG → replicas briefly behind (stale reads;
    possible data loss if the primary fails before replicating) — eventual consistency
→ trade-off: durability/consistency vs performance/availability
```

## இது ஏன் முக்கியமானது

பிரതிलिपि புரிந்துகொள்வது மূল్यবान், ஏனெனில் இது **data systems இல் availability மற்றும் read scaling க்கான ஒரு அடிப்படைப் நுட்பம் ஆகும்**, எனவே இது முக்கியமான system-design ஞ்ஞานம்.

பிரதிலிபि — servers முழுவதும் தரவின் நகலை பராமரிக்கும் — முக்கியமான நோக్్యங్களை பூरण करता है: **உपलब्धता** (redundancy மற்றும் failover மூலம் failures இலிருந்து உயிர் பிழைப்பது), **read scaling** (primary ஐ ஆফলோட் చేய்ய replicas இலிருந்து reads வழங்குவது, read-heavy workloads க்கு மதிப்புள்ளது), மற்றும் **புவியியல் விநியோகம்** (பயனர்களுக்கு அருகே நகலைகள் குறைந்த latency க்கு, மேலும் disaster recovery).

இந்த நோக்్యங்களை புரிந்துகொள்வது reliable, scalable data systems க்கு பிரतिलिपि அடிப்படை என்பதை स्पष्ट చేస్తుంది.

**වೌशลों** புरुण करता है — **primary-replica** (ek primary for writes replicating to read replicas — common, simple model great for read-heavy workloads, though primary is a write bottleneck) versus **multi-primary** (multiple nodes accepting writes, enabling write scaling மற்றும் geo-writes but requiring complex conflict resolution) — சரியான approach தேர్చుക్కోవడానికి అవश్యకం.

**synchronous vs asynchronous** trade-off ను புرుण చేस్కోవడం ప్రత్యేకంగా গুরुत్వపూర్ణం: **synchronous** replication (replicas confirm చేసేవరకు నిరీక్ష్తం) replicas consistent మరియు data loss ఆపుకుంటుంది కానీ slower, అయితే **asynchronous** replication (immediately acknowledge, background מ replicating) fast మరియు highly available కానీ **replication lag** (replicas briefly behind, stale reads causing మరియు possible data loss if primary fails before replicating — eventual consistency).

ఇది durability/consistency vs performance/availability trade-off ఒక key design decision.

Reputation fundamentally உپलப్ধత మరియు read scaling సం data systems బరుత్വం ఆందు కుందు వ్యూహం (primary-replica vs multi-primary) మరియు sync/async trade-offs significantly affect consistency, performance, మరియు availability, మరియు వాటిని فهम చేస్కోవడం data systems design కు ముఖ్యం, replication యొక్క ప్రత్యేకంగా ఓ ఆధారమైన నుపుట్ — availability మరియు read scaling क्षमতకు అవશ్యక నుపుట్, ఉపయుक్త strategy మరియు sync/async trade-offs నుండి, మరియు failures ఊర్ధ్వ చేసే మరియు read load నిర్వాహించే reliable, scalable data systems को designing కु కేంద్రీయం, replication యొక్క సిద్ధాంతం విలువైన, practically-relevant system-design knowledge.