Serializable Snapshot Isolation (SSI)

Documentation tagged with Serializable Snapshot Isolation (SSI) in the Geode graph database. SSI is an advanced concurrency control mechanism that provides true serializability without the performance overhead of traditional two-phase locking, making it the gold standard for ACID-compliant distributed databases. <h3 id="introduction-to-serializable-snapshot-isolation" class="position-relative d-flex align-items-center group"> Introduction to Serializable Snapshot Isolation <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="introduction-to-serializable-snapshot-isolation" aria-haspopup="dialog" aria-label="Share link: Introduction to Serializable Snapshot Isolation"> Share link </button> </h3><div id="headingShareModal" class="heading-share-modal" role="dialog" aria-modal="true" aria-labelledby="headingShareTitle" hidden> <div class="hsm-dialog" role="document"> <div class="hsm-header"> <h2 id="headingShareTitle" class="h6 mb-0 fw-bold">Share this section</h2> <button type="button" class="hsm-close" aria-label="Close"> </button> </div> <div class="hsm-body"> <label for="headingShareInput" class="form-label small text-muted mb-1 text-uppercase fw-bold" style="font-size: 0.7rem; letter-spacing: 0.5px;">Permalink</label> <div class="input-group mb-4 hsm-url-group"> <input id="headingShareInput" type="text" class="form-control font-monospace" readonly aria-readonly="true" style="font-size: 0.85rem;" /> <button class="btn btn-primary hsm-copy" type="button" aria-label="Copy" title="Copy"> </button> </div> <div class="small fw-bold mb-2 text-muted text-uppercase" style="font-size: 0.7rem; letter-spacing: 0.5px;">Share via</div> <div class="hsm-share-grid"> <a id="share-twitter" class="btn btn-outline-secondary w-100" target="_blank" rel="noopener noreferrer"> Twitter </a> <a id="share-linkedin" class="btn btn-outline-secondary w-100" target="_blank" rel="noopener noreferrer"> LinkedIn </a> <a id="share-facebook" class="btn btn-outline-secondary w-100" target="_blank" rel="noopener noreferrer"> Facebook </a> </div> </div> </div> </div> <style> .heading-share-modal { position: fixed; inset: 0; display: flex; justify-content: center; align-items: center; background: rgba(0, 0, 0, 0.6); z-index: 1050; padding: 1rem; backdrop-filter: blur(4px); -webkit-backdrop-filter: blur(4px); } .heading-share-modal[hidden] { display: none !important; } .hsm-dialog { max-width: 420px; width: 100%; background: var(--bs-body-bg, #fff); color: var(--bs-body-color, #212529); border: 1px solid var(--bs-border-color, rgba(0,0,0,0.1)); border-radius: 1rem; box-shadow: 0 25px 50px -12px rgba(0, 0, 0, 0.25); overflow: hidden; animation: hsm-fade-in 0.2s ease-out; } @keyframes hsm-fade-in { from { opacity: 0; transform: scale(0.95); } to { opacity: 1; transform: scale(1); } } [data-bs-theme="dark"] .hsm-dialog { background: #1e293b; border-color: rgba(255,255,255,0.1); color: #f8f9fa; } .hsm-header { display: flex; justify-content: space-between; align-items: center; padding: 1rem 1.5rem; border-bottom: 1px solid var(--bs-border-color, rgba(0,0,0,0.1)); background: rgba(0,0,0,0.02); } [data-bs-theme="dark"] .hsm-header { background: rgba(255,255,255,0.02); border-color: rgba(255,255,255,0.1); } .hsm-close { background: transparent; border: none; color: inherit; opacity: 0.5; padding: 0.25rem 0.5rem; border-radius: 0.25rem; font-size: 1.2rem; line-height: 1; transition: opacity 0.2s; } .hsm-close:hover { opacity: 1; } .hsm-body { padding: 1.5rem; } .hsm-url-group { display: flex !important; align-items: stretch; } .hsm-url-group .form-control { flex: 1; min-width: 0; margin: 0; background: var(--bs-secondary-bg, #f8f9fa); border-color: var(--bs-border-color, #dee2e6); border-top-right-radius: 0; border-bottom-right-radius: 0; height: 42px; } .hsm-url-group .btn { flex: 0 0 auto; margin: 0; margin-left: -1px; border-top-left-radius: 0; border-bottom-left-radius: 0; height: 42px; display: flex; align-items: center; justify-content: center; padding: 0 1.25rem; z-index: 2; } [data-bs-theme="dark"] .hsm-url-group .form-control { background: #0f172a; border-color: #334155; color: #e2e8f0; } .hsm-share-grid { display: flex; flex-direction: column; gap: 0.5rem; } .hsm-share-grid .btn { display: flex; align-items: center; justify-content: center; font-size: 0.9rem; padding: 0.6rem; border-color: var(--bs-border-color); width: 100%; } [data-bs-theme="dark"] .hsm-share-grid .btn { color: #e2e8f0; border-color: #475569; } [data-bs-theme="dark"] .hsm-share-grid .btn:hover { background: #334155; border-color: #cbd5e1; } </style> <script> (function(){ const modal = document.getElementById('headingShareModal'); if(!modal) return; const input = modal.querySelector('#headingShareInput'); const copyBtn = modal.querySelector('.hsm-copy'); const twitter = modal.querySelector('#share-twitter'); const linkedin = modal.querySelector('#share-linkedin'); const facebook = modal.querySelector('#share-facebook'); const closeBtn = modal.querySelector('.hsm-close'); let lastFocus=null; let trapBound=false; function buildUrl(id){ return window.location.origin + window.location.pathname + '#' + id; } function isOpen(){ return !modal.hasAttribute('hidden'); } function hydrate(id){ const url=buildUrl(id); input.value=url; const enc=encodeURIComponent(url); const text=encodeURIComponent(document.title); if(twitter) twitter.href=`https://twitter.com/intent/tweet?url=${enc}&text=${text}`; if(linkedin) linkedin.href=`https://www.linkedin.com/sharing/share-offsite/?url=${enc}`; if(facebook) facebook.href=`https://www.facebook.com/sharer/sharer.php?u=${enc}`; } function openModal(id){ lastFocus=document.activeElement; hydrate(id); if(!isOpen()){ modal.removeAttribute('hidden'); } requestAnimationFrame(()=>{ input.focus(); }); trapFocus(); } function closeModal(){ if(!isOpen()) return; modal.setAttribute('hidden',''); if(lastFocus && typeof lastFocus.focus==='function') lastFocus.focus(); } function copyCurrent(){ try{ navigator.clipboard.writeText(input.value).then(()=>feedback(true),()=>fallback()); } catch(e){ fallback(); } } function fallback(){ input.select(); try{ document.execCommand('copy'); feedback(true);}catch(e){ feedback(false);} } function feedback(ok){ if(!copyBtn) return; const icon=copyBtn.querySelector('i'); if(!icon) return; const prev=copyBtn.getAttribute('data-prev')||icon.className; if(!copyBtn.getAttribute('data-prev')) copyBtn.setAttribute('data-prev',prev); icon.className= ok ? 'fa-duotone fa-clipboard-check':'fa-duotone fa-circle-exclamation'; setTimeout(()=>{ icon.className=prev; },1800); } function handleShareClick(e){ e.preventDefault(); const btn=e.currentTarget; const id=btn.getAttribute('data-share-target'); if(id) openModal(id); } function bindShareButtons(){ document.querySelectorAll('.h-share').forEach(btn=>{ if(!btn.dataset.hShareBound){ btn.addEventListener('click', handleShareClick); btn.dataset.hShareBound='1'; } }); } bindShareButtons(); if(document.readyState==='loading'){ document.addEventListener('DOMContentLoaded', bindShareButtons); } else { requestAnimationFrame(bindShareButtons); } document.addEventListener('click', function(e){ const shareBtn=e.target.closest && e.target.closest('.h-share'); if(shareBtn && !shareBtn.dataset.hShareBound){ handleShareClick.call(shareBtn, e); } }, true); document.addEventListener('click', e=>{ if(e.target===modal) closeModal(); if(e.target.closest && e.target.closest('.hsm-close')){ e.preventDefault(); closeModal(); } if(copyBtn && (e.target===copyBtn || (e.target.closest && e.target.closest('.hsm-copy')))) { e.preventDefault(); copyCurrent(); } }); document.addEventListener('keydown', e=>{ if(e.key==='Escape' && isOpen()) closeModal(); }); function trapFocus(){ if(trapBound) return; trapBound=true; modal.addEventListener('keydown', f=>{ if(f.key==='Tab' && isOpen()){ const focusable=[...modal.querySelectorAll('a[href],button,input,textarea,select,[tabindex]:not([tabindex="-1"])')].filter(el=>!el.hasAttribute('disabled')); if(!focusable.length) return; const first=focusable[0]; const last=focusable[focusable.length-1]; if(f.shiftKey && document.activeElement===first){ f.preventDefault(); last.focus(); } else if(!f.shiftKey && document.activeElement===last){ f.preventDefault(); first.focus(); } } }); } if(closeBtn) closeBtn.addEventListener('click', e=>{ e.preventDefault(); closeModal(); }); })(); </script>Serializable Snapshot Isolation (SSI) represents the pinnacle of concurrency control mechanisms—it provides the strongest isolation guarantee (serializability) while maintaining the high concurrency benefits of snapshot isolation. Published in 2008 by Michael James Cahill, SSI solved a decades-old problem: how to achieve true serializability without sacrificing performance. Traditional serializability implementations use two-phase locking, which forces transactions to acquire locks before accessing data. This creates contention bottlenecks—readers block writers, writers block readers, and throughput plummets under concurrent load. Snapshot isolation (SI) solved the performance problem by allowing readers and writers to proceed concurrently, but SI permits certain anomalies like write skew that violate serializability. SSI bridges this gap. It starts with snapshot isolation’s optimistic concurrency model, then adds lightweight conflict detection to catch the specific patterns that would violate serializability. When SSI detects a dangerous structure, it aborts one transaction to maintain correctness. The key insight: these dangerous patterns are rare in practice, so SSI achieves near-SI performance with full serializability guarantees. Geode implements SSI as its highest isolation level, providing true ACID semantics for applications that require it. This makes Geode suitable for financial systems, inventory management, and other domains where correctness cannot be compromised. <h3 id="understanding-serializability" class="position-relative d-flex align-items-center group"> Understanding Serializability <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="understanding-serializability" aria-haspopup="dialog" aria-label="Share link: Understanding Serializability"> Share link </button> </h3>Serializability means transaction executions are equivalent to some serial (one-at-a-time) execution. If transactions T1 and T2 run concurrently, the result must match either: <ul> <li>T1 runs completely, then T2 runs completely</li> <li>T2 runs completely, then T1 runs completely</li> </ul> This guarantee prevents all concurrency anomalies: <h4 id="write-skew-anomaly" class="position-relative d-flex align-items-center group"> Write Skew Anomaly <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="write-skew-anomaly" aria-haspopup="dialog" aria-label="Share link: Write Skew Anomaly"> Share link </button> </h4>The classic SSI problem case: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Initial state: account1.balance = $100, account2.balance = $100 -- Business rule: total balance must stay >= $100 -- Transaction 1 BEGIN TRANSACTION ISOLATION LEVEL SERIALIZABLE; MATCH (a1:Account {id: 'account1'}), (a2:Account {id: 'account2'}) WHERE a1.balance + a2.balance >= 100 SET a1.balance = a1.balance - 80; COMMIT; -- Transaction 2 (concurrent) BEGIN TRANSACTION ISOLATION LEVEL SERIALIZABLE; MATCH (a1:Account {id: 'account1'}), (a2:Account {id: 'account2'}) WHERE a1.balance + a2.balance >= 100 SET a2.balance = a2.balance - 80; COMMIT; -- Result: account1 = $20, account2 = $20, total = $40 (violates constraint!) </code></pre></div>Under basic snapshot isolation, both transactions see the initial $200 total, both pass the constraint check, and both commit—violating the business rule. SSI detects this dangerous structure and aborts one transaction. <h4 id="phantom-reads" class="position-relative d-flex align-items-center group"> Phantom Reads <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="phantom-reads" aria-haspopup="dialog" aria-label="Share link: Phantom Reads"> Share link </button> </h4>SSI also prevents phantoms: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Transaction 1 BEGIN; MATCH (p:Person) WHERE p.age < 18 RETURN count(*) AS minors; -- Returns 5 -- Transaction 2 (concurrent) BEGIN; INSERT (:Person {name: 'Child', age: 10}); COMMIT; -- Transaction 1 continues MATCH (p:Person) WHERE p.age < 18 RETURN count(*) AS minors; -- Returns 6 in SI COMMIT; </code></pre></div>Basic SI would allow the count to change within T1. SSI detects the conflict and aborts one transaction. <h3 id="how-ssi-works-in-geode" class="position-relative d-flex align-items-center group"> How SSI Works in Geode <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="how-ssi-works-in-geode" aria-haspopup="dialog" aria-label="Share link: How SSI Works in Geode"> Share link </button> </h3> <h4 id="conflict-detection" class="position-relative d-flex align-items-center group"> Conflict Detection <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="conflict-detection" aria-haspopup="dialog" aria-label="Share link: Conflict Detection"> Share link </button> </h4>SSI tracks two types of dependencies between transactions: <ol> <li>Read-Write (rw) Dependencies: T1 reads data that T2 modifies</li> <li>Write-Read (wr) Dependencies: T1 writes data that T2 reads</li> </ol> A dangerous structure exists when there’s a cycle of rw dependencies: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-fallback" data-lang="fallback">T1 --(rw)--> T2 --(rw)--> T3 --(rw)--> T1 </code></pre></div>This pattern is called a “dangerous structure” or “pivot.” When detected, Geode aborts one transaction in the cycle to break it. <h4 id="read-tracking" class="position-relative d-flex align-items-center group"> Read Tracking <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="read-tracking" aria-haspopup="dialog" aria-label="Share link: Read Tracking"> Share link </button> </h4>Geode maintains read sets for each transaction: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-fallback" data-lang="fallback">Transaction T1 read set: - Node(Person, id=123) version 42 - Node(Person, id=456) version 38 - Relationship(KNOWS, id=789) version 51 </code></pre></div>When another transaction modifies these items, Geode records an rw-dependency from the reading transaction to the writing transaction. <h4 id="write-tracking" class="position-relative d-flex align-items-center group"> Write Tracking <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="write-tracking" aria-haspopup="dialog" aria-label="Share link: Write Tracking"> Share link </button> </h4>Geode maintains write sets for each transaction: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-fallback" data-lang="fallback">Transaction T2 write set: - Node(Person, id=123) version 43 (new) - Relationship(KNOWS, id=999) version 52 (new) </code></pre></div>When another transaction reads items in the write set, Geode records a wr-dependency. <h4 id="commit-time-validation" class="position-relative d-flex align-items-center group"> Commit-Time Validation <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="commit-time-validation" aria-haspopup="dialog" aria-label="Share link: Commit-Time Validation"> Share link </button> </h4>At commit time, Geode checks for dangerous structures: <ol> <li>Collect all transactions that have rw or wr dependencies with this transaction</li> <li>Check if any dependency cycle exists</li> <li>If a cycle exists, abort this transaction with a serialization failure error</li> <li>If no cycle, commit successfully</li> </ol> This validation is fast—typically microseconds—because the dependency graph is small. <h4 id="lock-free-implementation" class="position-relative d-flex align-items-center group"> Lock-Free Implementation <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="lock-free-implementation" aria-haspopup="dialog" aria-label="Share link: Lock-Free Implementation"> Share link </button> </h4>SSI is completely lock-free: <ul> <li>Readers never block writers</li> <li>Writers never block readers</li> <li>Writers only block other writers on the same item (write-write conflict)</li> <li>Detection happens optimistically at commit time</li> </ul> This enables linear scalability of concurrent transactions. <h3 id="production-use-cases" class="position-relative d-flex align-items-center group"> Production Use Cases <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="production-use-cases" aria-haspopup="dialog" aria-label="Share link: Production Use Cases"> Share link </button> </h3> <h4 id="financial-transactions" class="position-relative d-flex align-items-center group"> Financial Transactions <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="financial-transactions" aria-haspopup="dialog" aria-label="Share link: Financial Transactions"> Share link </button> </h4>SSI is essential for financial correctness: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Account transfer with serializability BEGIN TRANSACTION ISOLATION LEVEL SERIALIZABLE; MATCH (from:Account {id: $fromId}) WHERE from.balance >= $amount SET from.balance = from.balance - $amount; MATCH (to:Account {id: $toId}) SET to.balance = to.balance + $amount; INSERT (:AuditLog { timestamp: now(), from: $fromId, to: $toId, amount: $amount }); COMMIT; </code></pre></div>SSI guarantees no lost updates, no double-spending, and no constraint violations. <h4 id="inventory-management" class="position-relative d-flex align-items-center group"> Inventory Management <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="inventory-management" aria-haspopup="dialog" aria-label="Share link: Inventory Management"> Share link </button> </h4>Prevent overselling in concurrent environments: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">BEGIN TRANSACTION ISOLATION LEVEL SERIALIZABLE; MATCH (product:Product {sku: $sku}) WHERE product.quantity >= $orderQty SET product.quantity = product.quantity - $orderQty; INSERT (:Order { product_sku: $sku, quantity: $orderQty, customer: $customerId, timestamp: now() }); COMMIT; </code></pre></div>Multiple concurrent orders won’t exceed available inventory. <h4 id="constraint-enforcement" class="position-relative d-flex align-items-center group"> Constraint Enforcement <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="constraint-enforcement" aria-haspopup="dialog" aria-label="Share link: Constraint Enforcement"> Share link </button> </h4>Enforce complex multi-record constraints: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Ensure department budget not exceeded BEGIN TRANSACTION ISOLATION LEVEL SERIALIZABLE; MATCH (d:Department {id: $deptId})-[:HAS_EMPLOYEE]->(e:Employee) WITH d, sum(e.salary) AS total_salaries WHERE total_salaries + $newSalary <= d.budget INSERT (d)-[:HAS_EMPLOYEE]->(:Employee { name: $name, salary: $newSalary }); COMMIT; </code></pre></div>SSI prevents concurrent hires from violating budget constraints. <h3 id="advanced-ssi-patterns" class="position-relative d-flex align-items-center group"> Advanced SSI Patterns <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="advanced-ssi-patterns" aria-haspopup="dialog" aria-label="Share link: Advanced SSI Patterns"> Share link </button> </h3> <h4 id="read-your-writes-consistency" class="position-relative d-flex align-items-center group"> Read-Your-Writes Consistency <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="read-your-writes-consistency" aria-haspopup="dialog" aria-label="Share link: Read-Your-Writes Consistency"> Share link </button> </h4>Ensure transactions see their own writes: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-python" data-lang="python">async with client.connection() as tx: # Isolation is configured server-side await tx.begin() # Write await tx.execute(""" CREATE (u:User {id: $id, name: $name}) """, {"id": 123, "name": "Alice"}) # Read own write result, _ = await tx.query(""" MATCH (u:User {id: $id}) RETURN u.name """, {"id": 123}) assert result.rows[0]['u.name'] == "Alice" # Always true </code></pre></div> <h4 id="monotonic-reads" class="position-relative d-flex align-items-center group"> Monotonic Reads <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="monotonic-reads" aria-haspopup="dialog" aria-label="Share link: Monotonic Reads"> Share link </button> </h4>Guarantee forward progress: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-python" data-lang="python"># Read from consistent snapshot snapshot_time = None async def read_consistent(client, query): global snapshot_time async with client.connection() as tx: # Isolation is configured server-side await tx.begin() if snapshot_time: await tx.execute(f"SET TRANSACTION SNAPSHOT '{snapshot_time}'") result, _ = await tx.query(query) if not snapshot_time: snapshot_time = await tx.get_snapshot_timestamp() return result </code></pre></div> <h4 id="retry-logic-with-exponential-backoff" class="position-relative d-flex align-items-center group"> Retry Logic with Exponential Backoff <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="retry-logic-with-exponential-backoff" aria-haspopup="dialog" aria-label="Share link: Retry Logic with Exponential Backoff"> Share link </button> </h4>Handle serialization failures gracefully: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-python" data-lang="python">import asyncio from tenacity import retry, stop_after_attempt, wait_exponential @retry( stop=stop_after_attempt(10), wait=wait_exponential(multiplier=1, min=0.1, max=10), retry=retry_if_exception_type(SerializationFailure) ) async def execute_with_retry(client, query, params=None): """Execute query with automatic retry on serialization failures""" async with client.connection() as tx: # Isolation is configured server-side await tx.begin() result, _ = await tx.query(query, params) await tx.commit() return result # Usage result = await execute_with_retry(client, """ MATCH (product:Product {sku: $sku}) WHERE product.quantity >= $qty SET product.quantity = product.quantity - $qty """, {"sku": "WIDGET-001", "qty": 5}) </code></pre></div> <h3 id="performance-tuning-for-ssi" class="position-relative d-flex align-items-center group"> Performance Tuning for SSI <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="performance-tuning-for-ssi" aria-haspopup="dialog" aria-label="Share link: Performance Tuning for SSI"> Share link </button> </h3> <h4 id="transaction-duration-optimization" class="position-relative d-flex align-items-center group"> Transaction Duration Optimization <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="transaction-duration-optimization" aria-haspopup="dialog" aria-label="Share link: Transaction Duration Optimization"> Share link </button> </h4>Keep transactions short to reduce conflicts: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-python" data-lang="python"># ANTI-PATTERN: Long transaction with non-critical work async with client.connection() as tx: # Isolation is configured server-side await tx.begin() # External API call (slow!) customer_data = await fetch_customer_from_api(customer_id) # Complex computation recommendations = compute_recommendations(customer_data) # Critical database update await tx.execute("CREATE (o:Order {data: $data})", {"data": recommendations}) # PATTERN: Move non-critical work outside transaction customer_data = await fetch_customer_from_api(customer_id) recommendations = compute_recommendations(customer_data) # Short transaction for critical section async with client.connection() as tx: # Isolation is configured server-side await tx.begin() await tx.execute("CREATE (o:Order {data: $data})", {"data": recommendations}) </code></pre></div> <h4 id="access-order-consistency" class="position-relative d-flex align-items-center group"> Access Order Consistency <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="access-order-consistency" aria-haspopup="dialog" aria-label="Share link: Access Order Consistency"> Share link </button> </h4>Access data in consistent order to reduce deadlocks: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-python" data-lang="python"># ANTI-PATTERN: Random access order async def transfer_random_order(from_id, to_id, amount): async with client.connection() as tx: # Isolation is configured server-side await tx.begin() await tx.execute(""" MATCH (from:Account {id: $from_id}) SET from.balance = from.balance - $amount """, {"from_id": from_id, "amount": amount}) await tx.execute(""" MATCH (to:Account {id: $to_id}) SET to.balance = to.balance + $amount """, {"to_id": to_id, "amount": amount}) # PATTERN: Consistent access order async def transfer_ordered(from_id, to_id, amount): # Always access accounts in ID order first_id, second_id = (from_id, to_id) if from_id < to_id else (to_id, from_id) async with client.connection() as tx: # Isolation is configured server-side await tx.begin() await tx.execute(""" MATCH (a1:Account {id: $id1}), (a2:Account {id: $id2}) SET a1.balance = CASE WHEN $id1 = $from THEN a1.balance - $amt ELSE a1.balance + $amt END, a2.balance = CASE WHEN $id2 = $from THEN a2.balance - $amt ELSE a2.balance + $amt END """, {"id1": first_id, "id2": second_id, "from": from_id, "amt": amount}) </code></pre></div> <h4 id="monitoring-ssi-performance" class="position-relative d-flex align-items-center group"> Monitoring SSI Performance <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="monitoring-ssi-performance" aria-haspopup="dialog" aria-label="Share link: Monitoring SSI Performance"> Share link </button> </h4>Track serialization failures: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-python" data-lang="python">from geode_client import QueryError from prometheus_client import Counter, Histogram serialization_failures = Counter('geode_serialization_failures', 'Total serialization failures') transaction_duration = Histogram('geode_transaction_duration_seconds', 'Transaction duration') async def monitored_transaction(client, operation): start_time = time.time() try: async with client.connection() as tx: # Isolation is configured server-side await tx.begin() result = await operation(tx) await tx.commit() return result except QueryError as exc: if "SERIALIZATION" not in str(exc): raise serialization_failures.inc() raise finally: duration = time.time() - start_time transaction_duration.observe(duration) </code></pre></div> <h4 id="adaptive-isolation-levels" class="position-relative d-flex align-items-center group"> Adaptive Isolation Levels <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="adaptive-isolation-levels" aria-haspopup="dialog" aria-label="Share link: Adaptive Isolation Levels"> Share link </button> </h4>Use SSI only when necessary: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-python" data-lang="python">class AdaptiveIsolation: def __init__(self, client): self.client = client self.failure_counts = {} async def execute_adaptive(self, key, query, params=None): """Automatically adjust isolation level based on failure rate""" failures = self.failure_counts.get(key, 0) try: async with self.client.connection() as conn: # Isolation is configured server-side await conn.begin() result, _ = await conn.query(query, params) await conn.commit() # Success - decay failure count if key in self.failure_counts: self.failure_counts[key] = max(0, self.failure_counts[key] - 1) return result except QueryError as exc: if "SERIALIZATION" not in str(exc): raise # Increment failure count self.failure_counts[key] = self.failure_counts.get(key, 0) + 1 raise </code></pre></div> <h3 id="troubleshooting-ssi-issues" class="position-relative d-flex align-items-center group"> Troubleshooting SSI Issues <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="troubleshooting-ssi-issues" aria-haspopup="dialog" aria-label="Share link: Troubleshooting SSI Issues"> Share link </button> </h3> <h4 id="high-abort-rates" class="position-relative d-flex align-items-center group"> High Abort Rates <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="high-abort-rates" aria-haspopup="dialog" aria-label="Share link: High Abort Rates"> Share link </button> </h4>Symptom: Many serialization failures Diagnosis: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-python" data-lang="python"># Check abort rate async def check_abort_rate(client): async with client.connection() as conn: stats, _ = await conn.query( """ SELECT COUNT(*) FILTER (WHERE status = 'aborted') AS aborted, COUNT(*) FILTER (WHERE status = 'committed') AS committed, COUNT(*) FILTER (WHERE status = 'aborted') * 100.0 / COUNT(*) AS abort_rate FROM system.transaction_log WHERE timestamp > now() - interval '1 hour' """ ) row = stats.rows[0] if stats.rows else None if row: abort_rate = float(row["abort_rate"].as_decimal) if abort_rate > 5.0: print(f"WARNING: High abort rate: {abort_rate:.2f}%") </code></pre></div>Solutions: <ul> <li>Reduce transaction duration</li> <li>Access data in consistent order</li> <li>Partition hotspot data</li> <li>Use lower isolation if acceptable</li> </ul> <h4 id="conflict-analysis" class="position-relative d-flex align-items-center group"> Conflict Analysis <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="conflict-analysis" aria-haspopup="dialog" aria-label="Share link: Conflict Analysis"> Share link </button> </h4>Identify conflicting transactions: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Find transactions with frequent conflicts SELECT t1.transaction_id AS tx1, t2.transaction_id AS tx2, COUNT(*) AS conflict_count FROM system.transaction_conflicts WHERE timestamp > now() - interval '1 hour' GROUP BY t1.transaction_id, t2.transaction_id ORDER BY conflict_count DESC LIMIT 20; </code></pre></div> <h4 id="performance-degradation" class="position-relative d-flex align-items-center group"> Performance Degradation <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="performance-degradation" aria-haspopup="dialog" aria-label="Share link: Performance Degradation"> Share link </button> </h4>Monitor commit latency: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-python" data-lang="python">import matplotlib.pyplot as plt async def plot_commit_latency(client): async with client.connection() as conn: stats, _ = await conn.query( """ SELECT date_trunc('minute', timestamp) AS minute, AVG(commit_duration_ms) AS avg_latency, MAX(commit_duration_ms) AS max_latency, PERCENTILE_CONT(0.95) WITHIN GROUP (ORDER BY commit_duration_ms) AS p95_latency FROM system.transaction_log WHERE timestamp > now() - interval '1 hour' AND status = 'committed' GROUP BY minute ORDER BY minute """ ) minutes = [row['minute'] for row in stats] avg = [row['avg_latency'] for row in stats] p95 = [row['p95_latency'] for row in stats] plt.plot(minutes, avg, label='Average') plt.plot(minutes, p95, label='P95') plt.xlabel('Time') plt.ylabel('Latency (ms)') plt.legend() plt.savefig('commit_latency.png') </code></pre></div> <h3 id="related-topics" class="position-relative d-flex align-items-center group"> Related Topics <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="related-topics" aria-haspopup="dialog" aria-label="Share link: Related Topics"> Share link </button> </h3><ul> <li><a href="/tags/mvcc/" >Multi-Version Concurrency Control (MVCC)</a> - Foundation for SSI</li> <li><a href="/tags/acid/" >ACID Transactions</a> - Serializability is the “I” in ACID</li> <li><a href="/tags/isolation/" >Isolation Levels</a> - Different isolation guarantees</li> <li><a href="/tags/concurrency/" >Concurrency Control</a> - Broader concurrency mechanisms</li> <li><a href="/tags/transactions/" >Transactions</a> - Transaction management</li> <li><a href="/tags/wal/" >Write-Ahead Logging (WAL)</a> - Durability mechanism</li> <li><a href="/tags/performance/" >Performance</a> - Performance implications</li> </ul> <h3 id="further-reading" class="position-relative d-flex align-items-center group"> Further Reading <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="further-reading" aria-haspopup="dialog" aria-label="Share link: Further Reading"> Share link </button> </h3> <h4 id="documentation" class="position-relative d-flex align-items-center group"> Documentation <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="documentation" aria-haspopup="dialog" aria-label="Share link: Documentation"> Share link </button> </h4><ul> <li><a href="/docs/transactions/" >Transactions Guide</a> - Complete transaction documentation</li> <li><a href="/docs/performance/" >Performance Optimization</a> - Performance tuning techniques</li> </ul> <h4 id="academic-papers" class="position-relative d-flex align-items-center group"> Academic Papers <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="academic-papers" aria-haspopup="dialog" aria-label="Share link: Academic Papers"> Share link </button> </h4><ul> <li>“Serializable Isolation for Snapshot Databases” (Cahill et al., 2008) - Original SSI paper</li> </ul> <h4 id="implementation-details" class="position-relative d-flex align-items-center group"> Implementation Details <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="implementation-details" aria-haspopup="dialog" aria-label="Share link: Implementation Details"> Share link </button> </h4><ul> <li><a href="/docs/architecture/" >Architecture Overview</a> - System architecture including SSI</li> <li><a href="/docs/architecture/distributed-systems/" >Distributed Systems</a> - Distributed transaction handling</li> </ul> Geode’s SSI implementation provides true serializability with excellent performance. By detecting dangerous structures at commit time rather than blocking during execution, SSI enables high-concurrency workloads while maintaining the strongest possible correctness guarantees.

Popular

Related Articles

Transactions and Data Integrity