Infrastructure as Code (IaC)
Systemsteuerung per Skript.
Modes: 1. One-way (Mirroring). 2. Two-way (Bidirectional). 3. Continuous (Real-time). Techniques: File-level vs Block-level sync, delta encoding, version vectors, last-writer-wins resolution.
graph LR
Center["Infrastructure as Code (IaC)"]:::main
Rel_synthetic_biology["synthetic-biology"]:::related -.-> Center
click Rel_synthetic_biology "/terms/synthetic-biology"
classDef main fill:#7c3aed,stroke:#8b5cf6,stroke-width:2px,color:white,font-weight:bold,rx:5,ry:5;
classDef pre fill:#0f172a,stroke:#3b82f6,color:#94a3b8,rx:5,ry:5;
classDef child fill:#0f172a,stroke:#10b981,color:#94a3b8,rx:5,ry:5;
classDef related fill:#0f172a,stroke:#8b5cf6,stroke-dasharray: 5 5,color:#94a3b8,rx:5,ry:5;
linkStyle default stroke:#4b5563,stroke-width:2px;
🧒 Erkläre es wie einem 5-Jährigen
Ein Kochrezept für Server.
🤓 Expert Deep Dive
Technically, synchronization is governed by the 'CAP Theorem' (Consistency, Availability, Partition Tolerance). In a distributed system, you must trade off between 'Strong Consistency' (all nodes see the same data at the same time) and 'High Availability' (the system stays up even if some parts fail). 'Eventual Consistency' is a common model where the system guarantees that if no new updates are made, all nodes will eventually converge to the same state. Implementation methods include 'Change Data Capture' (CDC), which monitors database logs for changes, and 'Consensus [Algorithms](/de/terms/consensus-algorithms)' like Raft or Paxos, which allow a cluster of servers to agree on a single 'Truth' in the presence of failures.