Reviewed by Aditya Kumar · Last reviewed 2026-03-24
**Techniques:** (1) 2PC—coordinator commits/aborts all. (2) Saga—compensating tx for eventual consistency. (3) Distributed tx (Percolator/Spanner). (4) Eventual + conflict resolution (CRDTs, vector clocks)....
Techniques: (1) 2PC—coordinator commits/aborts all. (2) Saga—compensating tx for eventual consistency. (3) Distributed tx (Percolator/Spanner). (4) Eventual + conflict resolution (CRDTs, vector clocks). (5) Strong consistency where needed—single-partition writes.
Architecture Diagram:
[Client] --> [Coordinator]
| |
v v
[Partition A] [Partition B] [Partition C]
| | |
+----2PC Phase 1 (Prepare)----+
| | |
+----2PC Phase 2 (Commit)-----+
Trade-off: Strong consistency limits scale; choose per use case.
Pro-Move: Choose consistency level per use case with rationale. Red Flag: Global strong consistency for scale.
According to DataEngPrep.tech, this is one of the most frequently asked General/Other interview questions, reported at 1 company. DataEngPrep.tech maintains an editor-reviewed database of 1,863 data engineering interview questions across 7 categories.