Challenge 6c: Totally-Available, Read Committed Transactions

desccode

Leveling up our transaction system with an extra guarantee: no dirty reads. We've upgraded our consistency model while keeping total availability.

How it Works

Versioned Key-Value Store

Isolation & Replication

Why This Works

  1. Versioned Values: Only committed values are visible to reads

  2. Transaction Staging: Buffer all writes until commit

  3. Atomic Commits: All writes become visible at once

  4. Async Replication: Fire-and-forget keeps us totally available

  5. No Wait-for-Ack: We keep going even if nodes are partitioned

Trade-offs

Pros:

Cons:

The subtle art of keeping enough consistency to pass the test while staying totally available. i think this was the last challenge, so ill see you when i see you!


ref: Read Committed prohibits: