TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Versioning versus Coordination

65 pointsby burntcaramel3 months ago

2 comments

Olreich3 months ago
How do we guarantee &quot;T3 submitted at T+300ns&quot; reads the rows that are committed by T1 and T2 at T+100ns and T+200ns? I guess the answer is that the minimum transaction time for consistency is 5 minutes? At that point, don&#x27;t you lose a lot of the scalability and usefulness?<p>It feels very much like the &quot;read&quot; in the &quot;read-after-write consistency&quot; is usually forgotten, hand-waved away with &quot;eventual consistency&quot;, or is actually just a single node handling the coordination somewhere, leading us to not having nearly as scalable a system as we are promised by the database.
Willingham3 months ago
Great article, allowed me to learn about multi version concurrency control which I had never heard of, and in researching the topic I learned about optimistic concurrency control which I found even more interesting. It seems these two could be used in conjunction; OCC for efficient updates. MVCC for clean reads. Excited to play with these patterns in future projects (: