Tag: Transaction Management

Transaction management is a cornerstone of Geode’s enterprise-ready architecture. Unlike many graph databases that sacrifice consistency for performance, Geode provides full ACID guarantees with Serializable Snapshot Isolation (SSI), ensuring your data remains consistent even under high concurrency and complex workloads. Geode’s transaction system is built on Multi-Version Concurrency Control (MVCC), which enables high-performance concurrent access without locking readers. Combined with Write-Ahead Logging (WAL) for durability and savepoint support for complex transaction logic, Geode delivers the reliability and correctness required for mission-critical applications. This comprehensive guide explores transaction concepts, usage patterns, and best practices for leveraging Geode’s transaction capabilities effectively. <h3 id="core-transaction-concepts" class="position-relative d-flex align-items-center group"> Core Transaction Concepts <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="core-transaction-concepts" aria-haspopup="dialog" aria-label="Share link: Core Transaction Concepts"> 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>ACID Guarantees: Geode enforces all four ACID properties: <ul> <li>Atomicity: Transactions execute completely or not at all</li> <li>Consistency: Transactions maintain all integrity constraints</li> <li>Isolation: Concurrent transactions don’t interfere with each other</li> <li>Durability: Committed changes survive system failures</li> </ul> Serializable Snapshot Isolation (SSI): Geode implements the strongest isolation level, preventing all anomalies including phantom reads, non-repeatable reads, and serialization anomalies. Your transactions execute as if they were run serially, even when running concurrently. Multi-Version Concurrency Control (MVCC): Instead of locking, Geode maintains multiple versions of each graph element. Readers access consistent snapshots without blocking writers, and writers don’t block readers. This architecture delivers excellent concurrency while maintaining strict consistency. Write-Ahead Logging (WAL): Every change is first written to a durable log before being applied to the database. If the system crashes, Geode can recover to a consistent state by replaying the WAL. <h3 id="transaction-lifecycle-in-geode" class="position-relative d-flex align-items-center group"> Transaction Lifecycle 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="transaction-lifecycle-in-geode" aria-haspopup="dialog" aria-label="Share link: Transaction Lifecycle in Geode"> Share link </button> </h3>Understanding the transaction lifecycle helps you write correct and efficient code: <ol> <li>BEGIN: Start a new transaction, creating a consistent snapshot of the database</li> <li>EXECUTE: Run GQL queries and mutations within the transaction context</li> <li>COMMIT: Persist all changes durably and make them visible to other transactions</li> <li>ROLLBACK: Abort the transaction and discard all changes</li> </ol> All database operations in Geode execute within a transaction context. If you don’t explicitly begin a transaction, Geode automatically wraps each statement in its own implicit transaction. <h3 id="using-transactions-in-gql" class="position-relative d-flex align-items-center group"> Using Transactions in GQL <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="using-transactions-in-gql" aria-haspopup="dialog" aria-label="Share link: Using Transactions in GQL"> Share link </button> </h3>Geode provides standard SQL-style transaction control: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Explicit transaction START TRANSACTION; -- Create nodes and relationships MATCH (u:User {id: 123}) CREATE (p:Post {title: 'New Post', content: '...'}) CREATE (u)-[:POSTED]->(p); -- Update existing data MATCH (u:User {id: 456}) SET u.last_login = current_timestamp(); -- Commit all changes COMMIT; </code></pre></div>Rollback on Error: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">START TRANSACTION; MATCH (account:Account {id: 'A'}) SET account.balance = account.balance - 100; MATCH (account:Account {id: 'B'}) SET account.balance = account.balance + 100; -- If anything fails, rollback ROLLBACK; </code></pre></div>Read-Only Transactions: Optimize read-heavy workloads by declaring transactions as read-only: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">START TRANSACTION READ ONLY; MATCH (u:User)-[:FOLLOWS]->(other:User) RETURN u.name, collect(other.name); COMMIT; </code></pre></div> <h3 id="savepoints-for-complex-logic" class="position-relative d-flex align-items-center group"> Savepoints for Complex Logic <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="savepoints-for-complex-logic" aria-haspopup="dialog" aria-label="Share link: Savepoints for Complex Logic"> Share link </button> </h3>Savepoints enable partial rollback within a transaction, useful for implementing complex business logic: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">START TRANSACTION; -- Checkpoint 1 SAVEPOINT before_user_update; MATCH (u:User {id: 123}) SET u.name = 'New Name'; -- Checkpoint 2 SAVEPOINT before_post_creation; CREATE (p:Post {title: 'Draft Post'}); -- Oops, rollback post creation but keep user update ROLLBACK TO SAVEPOINT before_post_creation; -- Release the savepoint RELEASE SAVEPOINT before_user_update; COMMIT; </code></pre></div>Savepoint Use Cases: <ul> <li>Try-catch style error handling within transactions</li> <li>Implementing multi-step workflows with conditional logic</li> <li>Batch operations where some items may fail</li> <li>Testing changes before committing</li> </ul> <h3 id="transaction-isolation-and-concurrency" class="position-relative d-flex align-items-center group"> Transaction Isolation and Concurrency <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-isolation-and-concurrency" aria-haspopup="dialog" aria-label="Share link: Transaction Isolation and Concurrency"> Share link </button> </h3>Geode’s SSI implementation prevents concurrency anomalies while maintaining high performance: Preventing Lost Updates: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Transaction 1 START TRANSACTION; MATCH (u:User {id: 123}) SET u.login_count = u.login_count + 1; COMMIT; -- Transaction 2 (concurrent) START TRANSACTION; MATCH (u:User {id: 123}) SET u.last_login = current_timestamp(); COMMIT; </code></pre></div>Both transactions succeed without conflict. MVCC ensures each sees a consistent snapshot and updates are properly serialized. Detecting Write Conflicts: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Transaction 1 START TRANSACTION; MATCH (p:Product {id: 'PROD-1'}) WHERE p.stock > 0 SET p.stock = p.stock - 1; COMMIT; -- Transaction 2 (concurrent, same product) START TRANSACTION; MATCH (p:Product {id: 'PROD-1'}) WHERE p.stock > 0 SET p.stock = p.stock - 1; COMMIT; -- May fail with serialization error </code></pre></div>If both transactions attempt to modify the same product concurrently, one will succeed and the other will be aborted with a serialization error. Your application should retry the failed transaction. <h3 id="best-practices-for-transaction-management" class="position-relative d-flex align-items-center group"> Best Practices for Transaction 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="best-practices-for-transaction-management" aria-haspopup="dialog" aria-label="Share link: Best Practices for Transaction Management"> Share link </button> </h3>Keep Transactions Short: Long-running transactions hold resources and increase conflict probability. Execute transactions quickly and commit as soon as possible. Batch Operations Wisely: Group related operations into transactions, but avoid massive transactions that could exhaust memory: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Good: Reasonably sized batch START TRANSACTION; UNWIND $batch AS item CREATE (n:Node {id: item.id, data: item.data}); COMMIT; -- Avoid: Extremely large batches (>100k items) -- Instead, split into multiple transactions </code></pre></div>Use Read-Only Transactions: When you only need to query data, mark transactions as read-only for better performance and reduced conflict potential. Handle Serialization Errors: SSI may abort transactions due to conflicts. Implement retry logic with exponential backoff: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-python" data-lang="python">import time import random def execute_with_retry(query, max_attempts=3): for attempt in range(max_attempts): try: result = geode.execute(query) return result except SerializationError: if attempt == max_attempts - 1: raise time.sleep(random.uniform(0.01, 0.1) * (2 ** attempt)) </code></pre></div>Avoid Mixing Reads and Writes: When possible, separate read-heavy and write-heavy operations. This reduces contention and improves throughput. Use Savepoints for Complex Logic: Instead of aborting entire transactions, use savepoints to implement partial rollback logic. <h3 id="transaction-performance-optimization" class="position-relative d-flex align-items-center group"> Transaction Performance 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-performance-optimization" aria-haspopup="dialog" aria-label="Share link: Transaction Performance Optimization"> Share link </button> </h3>Connection Pooling: Reuse database connections to avoid transaction setup overhead: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-python" data-lang="python">from geode import ConnectionPool pool = ConnectionPool(max_connections=20) conn = pool.get_connection() conn.execute("START TRANSACTION") # ... operations ... conn.execute("COMMIT") pool.release(conn) </code></pre></div>Prepared Statements: Pre-compile frequently used queries to reduce parsing overhead: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-python" data-lang="python">stmt = geode.prepare(""" MATCH (u:User {id: $user_id}) SET u.last_login = current_timestamp() """) with geode.transaction(): stmt.execute(user_id=123) </code></pre></div>Deferred Constraints: For bulk operations, consider deferring constraint checking until commit time to avoid intermediate validation overhead. WAL Configuration: Tune WAL settings for your durability vs. performance requirements. Geode defaults to fsync on commit for maximum durability, but you can adjust for specific workloads. <h3 id="distributed-transaction-coordination" class="position-relative d-flex align-items-center group"> Distributed Transaction Coordination <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="distributed-transaction-coordination" aria-haspopup="dialog" aria-label="Share link: Distributed Transaction Coordination"> Share link </button> </h3>For multi-node deployments, Geode coordinates distributed transactions: Two-Phase Commit: Geode uses 2PC to ensure atomic commits across shards. The coordinator node ensures all participants commit or all abort. Distributed Deadlock Detection: Geode detects deadlocks across nodes and aborts one transaction to resolve the deadlock. Cross-Shard Transactions: Transactions can span multiple shards transparently: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">START TRANSACTION; -- May access data on different shards MATCH (u:User {id: 123}), (p:Product {id: 'PROD-1'}) CREATE (u)-[:PURCHASED]->(p); COMMIT; </code></pre></div> <h3 id="monitoring-transaction-health" class="position-relative d-flex align-items-center group"> Monitoring Transaction Health <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-transaction-health" aria-haspopup="dialog" aria-label="Share link: Monitoring Transaction Health"> Share link </button> </h3>Monitor key transaction metrics to ensure system health: <ul> <li>Transaction throughput: Commits per second</li> <li>Transaction latency: Time from START to COMMIT</li> <li>Abort rate: Percentage of transactions rolled back</li> <li>Conflict rate: Serialization failures per second</li> <li>Long-running transactions: Identify transactions holding resources</li> </ul> Use Geode’s metrics endpoints to track these values: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- View transaction statistics SHOW TRANSACTION STATS; -- Find long-running transactions SHOW TRANSACTIONS WHERE duration > 1000; </code></pre></div> <h3 id="troubleshooting-common-issues" class="position-relative d-flex align-items-center group"> Troubleshooting Common 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-common-issues" aria-haspopup="dialog" aria-label="Share link: Troubleshooting Common Issues"> Share link </button> </h3>High Abort Rates: If many transactions abort due to conflicts: <ul> <li>Reduce transaction duration</li> <li>Decrease batch sizes</li> <li>Implement exponential backoff retry logic</li> <li>Consider partitioning hot data</li> </ul> Deadlocks: If deadlocks occur frequently: <ul> <li>Access resources in consistent order across transactions</li> <li>Use shorter transactions</li> <li>Implement timeout logic</li> </ul> Performance Degradation: If transaction throughput drops: <ul> <li>Check for long-running transactions blocking others</li> <li>Monitor WAL write performance</li> <li>Verify sufficient connection pool capacity</li> <li>Review query execution plans for inefficient operations</li> </ul> <h3 id="advanced-transaction-features" class="position-relative d-flex align-items-center group"> Advanced Transaction Features <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-transaction-features" aria-haspopup="dialog" aria-label="Share link: Advanced Transaction Features"> Share link </button> </h3>Transaction Hooks: Register callbacks for transaction lifecycle events: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-python" data-lang="python">def on_commit(txn): # Trigger side effects after successful commit send_notification() geode.register_hook('after_commit', on_commit) </code></pre></div>Deferred Triggers: Execute logic after transaction commit without blocking the commit path. Read-Your-Writes Consistency: Geode guarantees that within a transaction, you always see your own writes, even before commit. <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/acid/" >ACID Compliance and Guarantees</a> </li> <li><a href="/tags/mvcc/" >Multi-Version Concurrency Control (MVCC)</a> </li> <li><a href="/tags/ssi/" >Serializable Snapshot Isolation (SSI)</a> </li> <li><a href="/tags/wal/" >Write-Ahead Logging (WAL)</a> </li> <li><a href="/tags/concurrency/" >Concurrency Control</a> </li> <li><a href="/tags/performance/" >Performance Tuning and Optimization</a> </li> <li><a href="/tags/data-integrity/" >Data Integrity and Consistency</a> </li> </ul> <h3 id="transaction-isolation-levels-in-detail" class="position-relative d-flex align-items-center group"> Transaction Isolation Levels in Detail <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-isolation-levels-in-detail" aria-haspopup="dialog" aria-label="Share link: Transaction Isolation Levels in Detail"> Share link </button> </h3> <h4 id="serializable-snapshot-isolation-ssi" class="position-relative d-flex align-items-center group"> Serializable Snapshot Isolation (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="serializable-snapshot-isolation-ssi" aria-haspopup="dialog" aria-label="Share link: Serializable Snapshot Isolation (SSI)"> Share link </button> </h4>Geode’s default isolation level provides the strongest guarantees: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-python" data-lang="python">from geode_client import Client async def ssi_example(): client = Client(host="localhost", port=3141) async with client.connection() as conn: # Default SSI behavior await conn.begin() result1, _ = await conn.query(""" MATCH (account:Account {id: $id}) RETURN account.balance AS balance """, {'id': 'acc_123'}) balance = result1.rows[0]["balance"].raw_value if result1.rows else 0 # Concurrent transaction cannot modify our snapshot if balance >= 100: await conn.execute(""" MATCH (account:Account {id: $id}) SET account.balance = account.balance - 100 """, {'id': 'acc_123'}) # Commits only if no conflicts detected await conn.commit() </code></pre></div> <h4 id="read-committed-isolation" class="position-relative d-flex align-items-center group"> Read Committed 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="read-committed-isolation" aria-haspopup="dialog" aria-label="Share link: Read Committed Isolation"> Share link </button> </h4>Lower isolation for higher concurrency: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-python" data-lang="python">async def read_committed_example(): client = Client(host="localhost", port=3141) async with client.connection() as conn: # If your deployment enables READ COMMITTED, the same flow applies await conn.begin() result1, _ = await conn.query(""" MATCH (product:Product {sku: $sku}) RETURN product.stock AS stock """, {'sku': 'PROD-123'}) # Another transaction commits here - you'll see the change result2, _ = await conn.query(""" MATCH (product:Product {sku: $sku}) RETURN product.stock AS stock """, {'sku': 'PROD-123'}) await conn.commit() </code></pre></div> <h3 id="advanced-transaction-patterns" class="position-relative d-flex align-items-center group"> Advanced Transaction 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-transaction-patterns" aria-haspopup="dialog" aria-label="Share link: Advanced Transaction Patterns"> Share link </button> </h3> <h4 id="two-phase-commit-for-distributed-transactions" class="position-relative d-flex align-items-center group"> Two-Phase Commit for Distributed 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="two-phase-commit-for-distributed-transactions" aria-haspopup="dialog" aria-label="Share link: Two-Phase Commit for Distributed Transactions"> Share link </button> </h4><div class="highlight"><pre tabindex="0" class="chroma"><code class="language-python" data-lang="python">class DistributedTransaction: def __init__(self, coordinator, participants): self.coordinator = coordinator self.participants = participants self.transaction_id = None async def execute(self, operations): """Execute distributed transaction with 2PC.""" self.transaction_id = generate_tx_id() # Phase 1: Prepare prepared = [] try: for participant, operation in zip(self.participants, operations): vote = await participant.prepare(self.transaction_id, operation) if vote != 'PREPARED': raise TransactionAbort(f"Participant {participant} voted abort") prepared.append(participant) # Phase 2: Commit for participant in prepared: await participant.commit(self.transaction_id) return True except Exception as e: # Rollback all prepared participants for participant in prepared: await participant.rollback(self.transaction_id) raise # Usage async def distributed_transfer(): coordinator = Client("coordinator:3141") shard1 = Client("shard1:3141") shard2 = Client("shard2:3141") tx = DistributedTransaction(coordinator, [shard1, shard2]) operations = [ # Debit from account on shard1 """ MATCH (account:Account {id: $from_id}) WHERE account.balance >= $amount SET account.balance = account.balance - $amount """, # Credit to account on shard2 """ MATCH (account:Account {id: $to_id}) SET account.balance = account.balance + $amount """ ] await tx.execute(operations) </code></pre></div> <h4 id="saga-pattern-for-long-running-transactions" class="position-relative d-flex align-items-center group"> Saga Pattern for Long-Running 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="saga-pattern-for-long-running-transactions" aria-haspopup="dialog" aria-label="Share link: Saga Pattern for Long-Running Transactions"> Share link </button> </h4><div class="highlight"><pre tabindex="0" class="chroma"><code class="language-python" data-lang="python">class Saga: """Saga pattern for managing long-running business transactions.""" def __init__(self, client): self.client = client self.steps = [] self.compensations = [] def add_step(self, forward_action, compensation_action): self.steps.append(forward_action) self.compensations.append(compensation_action) async def execute(self): """Execute saga with automatic compensation on failure.""" completed_steps = [] try: for i, step in enumerate(self.steps): await step() completed_steps.append(i) return True except Exception as e: # Compensate in reverse order for i in reversed(completed_steps): try: await self.compensations[i]() except Exception as comp_error: # Log compensation failure logger.error(f"Compensation failed for step {i}: {comp_error}") raise # Example: Order fulfillment saga async def order_fulfillment_saga(order_id): saga = Saga(client) # Step 1: Reserve inventory saga.add_step( forward_action=lambda: client.execute(""" MATCH (product:Product {sku: $sku}) WHERE product.stock >= $quantity SET product.stock = product.stock - $quantity, product.reserved = product.reserved + $quantity """, order.items), compensation_action=lambda: client.execute(""" MATCH (product:Product {sku: $sku}) SET product.stock = product.stock + $quantity, product.reserved = product.reserved - $quantity """, order.items) ) # Step 2: Process payment saga.add_step( forward_action=lambda: process_payment(order), compensation_action=lambda: refund_payment(order) ) # Step 3: Create shipment saga.add_step( forward_action=lambda: create_shipment(order), compensation_action=lambda: cancel_shipment(order) ) await saga.execute() </code></pre></div> <h4 id="optimistic-locking-with-version-numbers" class="position-relative d-flex align-items-center group"> Optimistic Locking with Version Numbers <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="optimistic-locking-with-version-numbers" aria-haspopup="dialog" aria-label="Share link: Optimistic Locking with Version Numbers"> Share link </button> </h4><div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Add version column to entities MATCH (product:Product) SET product.version = COALESCE(product.version, 0); -- Optimistic update MATCH (product:Product {sku: $sku}) WHERE product.version = $expected_version SET product.stock = product.stock - $quantity, product.version = product.version + 1 RETURN product.version AS new_version; -- If version mismatch, handle conflict </code></pre></div><div class="highlight"><pre tabindex="0" class="chroma"><code class="language-python" data-lang="python">async def optimistic_update(client, sku, quantity, max_retries=3): """Update with optimistic locking and retry.""" for attempt in range(max_retries): # Read current version result, _ = await client.query(""" MATCH (product:Product {sku: $sku}) RETURN product.version AS version, product.stock AS stock """, {'sku': sku}) row = result.rows[0] if result.rows else None if not row: raise ProductNotFound(sku) current_version = row['version'] current_stock = row['stock'] if current_stock < quantity: raise InsufficientStock(sku, current_stock, quantity) # Attempt update with version check try: update_result, _ = await client.query(""" MATCH (product:Product {sku: $sku}) WHERE product.version = $expected_version SET product.stock = product.stock - $quantity, product.version = product.version + 1 RETURN product.version AS new_version """, { 'sku': sku, 'expected_version': current_version, 'quantity': quantity }) updated_row = update_result.rows[0] if update_result.rows else None if updated_row: return updated_row['new_version'] else: # Version mismatch - retry if attempt < max_retries - 1: await asyncio.sleep(0.1 * (2 ** attempt)) continue else: raise OptimisticLockException(sku) except Exception as e: if attempt == max_retries - 1: raise await asyncio.sleep(0.1 * (2 ** attempt)) </code></pre></div> <h3 id="transaction-performance-tuning" class="position-relative d-flex align-items-center group"> Transaction Performance Tuning <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-performance-tuning" aria-haspopup="dialog" aria-label="Share link: Transaction Performance Tuning"> Share link </button> </h3> <h4 id="batch-operations-within-transactions" class="position-relative d-flex align-items-center group"> Batch Operations Within 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="batch-operations-within-transactions" aria-haspopup="dialog" aria-label="Share link: Batch Operations Within Transactions"> Share link </button> </h4><div class="highlight"><pre tabindex="0" class="chroma"><code class="language-python" data-lang="python">async def bulk_insert_with_batching(client, items, batch_size=1000): """Insert large datasets efficiently using batched transactions.""" total_inserted = 0 for i in range(0, len(items), batch_size): batch = items[i:i + batch_size] async with client.connection() as conn: await conn.begin() try: await conn.execute(""" UNWIND $batch AS item CREATE (p:Product { sku: item.sku, name: item.name, price: item.price, created_at: datetime() }) """, {'batch': batch}) total_inserted += len(batch) print(f"Inserted {total_inserted}/{len(items)} items") await conn.commit() except Exception: await conn.rollback() raise return total_inserted </code></pre></div> <h4 id="connection-pooling-for-transaction-throughput" class="position-relative d-flex align-items-center group"> Connection Pooling for Transaction Throughput <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="connection-pooling-for-transaction-throughput" aria-haspopup="dialog" aria-label="Share link: Connection Pooling for Transaction Throughput"> Share link </button> </h4><div class="highlight"><pre tabindex="0" class="chroma"><code class="language-python" data-lang="python">from geode_client import ConnectionPool class TransactionPool: def __init__(self, host, port, pool_size=20): self.pool = ConnectionPool( host=host, port=port, min_connections=5, max_connections=pool_size, connection_timeout=30.0, idle_timeout=300.0 ) async def execute_transaction(self, operations): """Execute transaction using pooled connection.""" conn = await self.pool.acquire() try: await conn.begin() try: results = [] for query, params in operations: result, _ = await conn.query(query, params) results.append([row for row in result.rows]) await conn.commit() return results except Exception: await conn.rollback() raise finally: await self.pool.release(conn) # Usage async def high_throughput_transactions(): pool = TransactionPool("localhost", 3141, pool_size=50) # Execute 10000 concurrent transactions tasks = [] for i in range(10000): operations = [ ("MATCH (u:User {id: $id}) SET u.last_seen = datetime()", {'id': i}) ] task = pool.execute_transaction(operations) tasks.append(task) results = await asyncio.gather(*tasks) print(f"Completed {len(results)} transactions") </code></pre></div> <h4 id="transaction-timeout-configuration" class="position-relative d-flex align-items-center group"> Transaction Timeout Configuration <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-timeout-configuration" aria-haspopup="dialog" aria-label="Share link: Transaction Timeout Configuration"> Share link </button> </h4><div class="highlight"><pre tabindex="0" class="chroma"><code class="language-python" data-lang="python">async def transaction_with_timeout(client, timeout_seconds=30): """Execute transaction with explicit timeout.""" try: async with asyncio.timeout(timeout_seconds): async with client.connection() as conn: await conn.begin() try: # Long-running operations await conn.execute(""" MATCH (n:Node) SET n.processed = true """) # More operations... await conn.commit() except Exception: await conn.rollback() raise except asyncio.TimeoutError: # Explicit rollback happens on exception logger.error(f"Transaction exceeded {timeout_seconds}s timeout") raise </code></pre></div> <h3 id="transaction-monitoring-and-debugging" class="position-relative d-flex align-items-center group"> Transaction Monitoring and Debugging <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-monitoring-and-debugging" aria-haspopup="dialog" aria-label="Share link: Transaction Monitoring and Debugging"> Share link </button> </h3> <h4 id="live-transaction-monitoring" class="position-relative d-flex align-items-center group"> Live Transaction Monitoring <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="live-transaction-monitoring" aria-haspopup="dialog" aria-label="Share link: Live Transaction Monitoring"> Share link </button> </h4><div class="highlight"><pre tabindex="0" class="chroma"><code class="language-python" data-lang="python">class TransactionMonitor: """Monitor active transactions and identify issues.""" def __init__(self, client): self.client = client async def list_active_transactions(self): """List all currently active transactions.""" result, _ = await self.client.query(""" CALL dbms.transactions.list() YIELD transactionId, username, database, elapsedTime, lockCount, status RETURN transactionId, username, duration.inSeconds(elapsedTime) AS seconds, lockCount, status ORDER BY elapsedTime DESC """) return [row for row in result.rows] async def find_blocked_transactions(self): """Identify transactions waiting on locks.""" result, _ = await self.client.query(""" CALL dbms.transactions.list() YIELD transactionId, status, waitingOn WHERE status = 'BLOCKED' RETURN transactionId, waitingOn """) return [row for row in result.rows] async def kill_long_running_transaction(self, tx_id): """Terminate a specific transaction.""" await self.client.execute(""" CALL dbms.transactions.terminate($tx_id) """, {'tx_id': tx_id}) # Usage async def monitor_transactions(): monitor = TransactionMonitor(client) # Find long-running transactions active = await monitor.list_active_transactions() for tx in active: if tx['seconds'] > 300: # 5 minutes print(f"Long-running tx: {tx['transactionId']} ({tx['seconds']}s)") await monitor.kill_long_running_transaction(tx['transactionId']) </code></pre></div> <h4 id="transaction-metrics-collection" class="position-relative d-flex align-items-center group"> Transaction Metrics Collection <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-metrics-collection" aria-haspopup="dialog" aria-label="Share link: Transaction Metrics Collection"> Share link </button> </h4><div class="highlight"><pre tabindex="0" class="chroma"><code class="language-python" data-lang="python">from prometheus_client import Counter, Histogram, Gauge # Metrics transaction_total = Counter( 'geode_transactions_total', 'Total transactions', ['status', 'isolation_level'] ) transaction_duration = Histogram( 'geode_transaction_duration_seconds', 'Transaction execution time', ['isolation_level'], buckets=[0.01, 0.1, 0.5, 1.0, 5.0, 10.0, 30.0] ) active_transactions = Gauge( 'geode_active_transactions', 'Number of active transactions' ) async def instrumented_transaction(client, operations, isolation=None): """Execute transaction with metrics collection.""" active_transactions.inc() start_time = time.time() try: async with client.connection() as conn: await conn.begin() try: for query, params in operations: await conn.execute(query, params) await conn.commit() except Exception: await conn.rollback() raise duration = time.time() - start_time transaction_total.labels( status='commit', isolation_level=isolation or 'serializable' ).inc() transaction_duration.labels( isolation_level=isolation or 'serializable' ).observe(duration) except Exception as e: transaction_total.labels( status='rollback', isolation_level=isolation or 'serializable' ).inc() raise finally: active_transactions.dec() </code></pre></div> <h3 id="distributed-transaction-coordination-1" class="position-relative d-flex align-items-center group"> Distributed Transaction Coordination <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="distributed-transaction-coordination-1" aria-haspopup="dialog" aria-label="Share link: Distributed Transaction Coordination"> Share link </button> </h3> <h4 id="cross-shard-transaction-example" class="position-relative d-flex align-items-center group"> Cross-Shard Transaction Example <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="cross-shard-transaction-example" aria-haspopup="dialog" aria-label="Share link: Cross-Shard Transaction Example"> Share link </button> </h4><div class="highlight"><pre tabindex="0" class="chroma"><code class="language-python" data-lang="python">async def cross_shard_transfer(amount, from_account, to_account): """Transfer money across database shards.""" # Determine shards from_shard = get_shard_for_account(from_account) to_shard = get_shard_for_account(to_account) if from_shard == to_shard: # Same shard - simple transaction async with from_shard.transaction(): await from_shard.execute(""" MATCH (from:Account {id: $from_id}), (to:Account {id: $to_id}) WHERE from.balance >= $amount SET from.balance = from.balance - $amount, to.balance = to.balance + $amount """, { 'from_id': from_account, 'to_id': to_account, 'amount': amount }) else: # Cross-shard - distributed transaction coordinator = DistributedTransactionCoordinator() async with coordinator.distributed_transaction([from_shard, to_shard]): # Debit from source shard await from_shard.execute(""" MATCH (account:Account {id: $id}) WHERE account.balance >= $amount SET account.balance = account.balance - $amount """, {'id': from_account, 'amount': amount}) # Credit to destination shard await to_shard.execute(""" MATCH (account:Account {id: $id}) SET account.balance = account.balance + $amount """, {'id': to_account, 'amount': amount}) # Coordinator ensures both commit or both rollback </code></pre></div> <h3 id="troubleshooting-transaction-issues" class="position-relative d-flex align-items-center group"> Troubleshooting Transaction 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-transaction-issues" aria-haspopup="dialog" aria-label="Share link: Troubleshooting Transaction Issues"> Share link </button> </h3> <h4 id="diagnosing-deadlocks" class="position-relative d-flex align-items-center group"> Diagnosing Deadlocks <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="diagnosing-deadlocks" aria-haspopup="dialog" aria-label="Share link: Diagnosing Deadlocks"> Share link </button> </h4><div class="highlight"><pre tabindex="0" class="chroma"><code class="language-python" data-lang="python">async def detect_deadlock_cycle(): """Identify circular wait dependencies.""" result, _ = await client.query(""" CALL dbms.transactions.graph() YIELD transaction, waitingFor WITH collect({tx: transaction, waits: waitingFor}) AS dependencies // Find cycles WITH dependencies UNWIND dependencies AS d1 UNWIND dependencies AS d2 WHERE d1.tx = d2.waits AND d2.tx = d1.waits RETURN DISTINCT d1.tx AS tx1, d2.tx AS tx2 """) cycles = [row for row in result.rows] if cycles: print("Deadlock detected!") for cycle in cycles: print(f" {cycle['tx1']} ↔ {cycle['tx2']}") return cycles </code></pre></div> <h4 id="resolving-high-abort-rates" class="position-relative d-flex align-items-center group"> Resolving 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="resolving-high-abort-rates" aria-haspopup="dialog" aria-label="Share link: Resolving High Abort Rates"> Share link </button> </h4><div class="highlight"><pre tabindex="0" class="chroma"><code class="language-python" data-lang="python">async def analyze_transaction_conflicts(): """Analyze conflict patterns to reduce abort rate.""" # Identify hot spots (frequently conflicted entities) result, _ = await client.query(""" CALL dbms.conflicts.summary() YIELD entity, conflictCount, avgRetries WHERE conflictCount > 100 RETURN entity, conflictCount, avgRetries ORDER BY conflictCount DESC LIMIT 20 """) hotspots = [row for row in result.rows] # Recommendations for hotspot in hotspots: entity = hotspot['entity'] conflicts = hotspot['conflictCount'] retries = hotspot['avgRetries'] print(f"Hot spot: {entity}") print(f" Conflicts: {conflicts}") print(f" Avg retries: {retries}") print(f" Recommendation: Consider sharding or using queuing") </code></pre></div> <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><ul> <li>ISO/IEC 39075:2024 GQL Transaction Semantics</li> <li>Transaction Processing: Concepts and Techniques</li> <li>Geode Architecture: MVCC Implementation</li> <li>Distributed Transaction Coordination</li> <li>Performance Tuning Guide</li> </ul>

Popular

Related Articles

Graph Query Language (GQL) Guide

Transactions and Data Integrity

Transaction Management Guide

Transactions