Optimistic concurrency is the whole design: event sourcing on Aurora DSQL
How an incident-command record built on Amazon Aurora DSQL stays consistent under cross-region contention, and why the property that lets the database survive a region loss is the same one that keeps the record from forking.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3984446) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Jonathan Posted on Jun 15 Optimistic concurrency is the whole design: event sourcing on Aurora DSQL #aws #database #distributedsystems #postgres Building Quorum on Aurora DSQL (3 Part Series) 1 Optimistic concurrency is the whole design: event sourcing on Aurora DSQL 2 Surviving the region you run in: failover on Aurora DSQL, and what the demo proves 3 I built a region-survivable system by directing an AI agent. An append-only decision log kept it coherent.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).