Tag: ACID Transactions

Documentation tagged with ACID Transactions in the Geode graph database. ACID (Atomicity, Consistency, Isolation, Durability) represents the fundamental guarantees that make database transactions reliable, ensuring data integrity even in the face of failures, concurrent access, and system crashes. <h3 id="introduction-to-acid" class="position-relative d-flex align-items-center group"> Introduction to ACID <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-acid" aria-haspopup="dialog" aria-label="Share link: Introduction to ACID"> 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 is the cornerstone of reliable data management. Coined by Andreas Reuter and Theo Härder in 1983, the ACID acronym describes four essential properties that transaction processing systems must provide to ensure data remains consistent and reliable: <ul> <li>Atomicity: Transactions are all-or-nothing operations</li> <li>Consistency: Transactions move the database from one valid state to another</li> <li>Isolation: Concurrent transactions don’t interfere with each other</li> <li>Durability: Committed data survives system failures</li> </ul> These properties matter profoundly in real-world systems. Without atomicity, partial updates could leave data in invalid states. Without consistency, business rules could be violated. Without isolation, concurrent users could corrupt each other’s work. Without durability, committed work could vanish in a crash. Geode implements full ACID semantics, making it suitable for mission-critical applications where correctness cannot be compromised. This positions Geode alongside traditional RDBMS systems in terms of reliability while providing the flexibility and performance of a native graph database. <h3 id="the-four-acid-properties" class="position-relative d-flex align-items-center group"> The Four ACID Properties <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="the-four-acid-properties" aria-haspopup="dialog" aria-label="Share link: The Four ACID Properties"> Share link </button> </h3> <h4 id="atomicity-all-or-nothing" class="position-relative d-flex align-items-center group"> Atomicity: All or Nothing <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="atomicity-all-or-nothing" aria-haspopup="dialog" aria-label="Share link: Atomicity: All or Nothing"> Share link </button> </h4>Atomicity means transactions execute completely or not at all. If any part of a transaction fails, the entire transaction rolls back, leaving no partial effects. <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">BEGIN TRANSACTION; -- Transfer $100 between accounts MATCH (from:Account {id: $fromId}) WHERE from.balance >= 100 SET from.balance = from.balance - 100; MATCH (to:Account {id: $toId}) SET to.balance = to.balance + 100; -- If this fails, everything rolls back INSERT (:AuditLog { timestamp: now(), from: $fromId, to: $toId, amount: 100 }); COMMIT; -- Either all succeed or all fail </code></pre></div>If the audit log insertion fails, atomicity guarantees that the account balances remain unchanged. The money doesn’t disappear into the ether. Implementation in Geode: Geode uses Write-Ahead Logging (WAL) to implement atomicity. All transaction operations are recorded in the WAL before being applied. On rollback, Geode reads the WAL to undo all changes. On crash, Geode replays or rolls back incomplete transactions during recovery. <h4 id="consistency-validity-preservation" class="position-relative d-flex align-items-center group"> Consistency: Validity Preservation <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="consistency-validity-preservation" aria-haspopup="dialog" aria-label="Share link: Consistency: Validity Preservation"> Share link </button> </h4>Consistency means transactions transform the database from one valid state to another, preserving all integrity constraints, business rules, and invariants. <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Consistency example: Referential integrity BEGIN TRANSACTION; -- Delete an order MATCH (order:Order {id: $orderId}) DELETE order; -- Must also delete related line items (constraint) MATCH (lineItem:LineItem)-[:BELONGS_TO]->(:Order {id: $orderId}) DELETE lineItem; COMMIT; -- Database remains consistent </code></pre></div>Consistency also includes application-level constraints: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Business rule: Total allocation cannot exceed 100% BEGIN TRANSACTION; MATCH (portfolio:Portfolio {id: $portfolioId})-[:HOLDS]->(asset:Asset) WITH portfolio, sum(asset.allocation) AS total_allocation WHERE total_allocation + $newAllocation <= 100 INSERT (portfolio)-[:HOLDS]->(:Asset { name: $assetName, allocation: $newAllocation }); COMMIT; </code></pre></div>Implementation in Geode: Geode enforces consistency through: <ul> <li>Constraint checking (uniqueness, type constraints, schema validation)</li> <li>Trigger execution (pre-commit and post-commit hooks)</li> <li>Transaction validation before commit</li> <li>Application-level constraint checking in WHERE clauses</li> </ul> <h4 id="isolation-concurrent-independence" class="position-relative d-flex align-items-center group"> Isolation: Concurrent Independence <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="isolation-concurrent-independence" aria-haspopup="dialog" aria-label="Share link: Isolation: Concurrent Independence"> Share link </button> </h4>Isolation means concurrent transactions behave as if they executed serially. One transaction’s intermediate states are invisible to others. Geode supports multiple isolation levels: Read Committed: See only committed data <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">SET TRANSACTION ISOLATION LEVEL READ COMMITTED; -- Won't see uncommitted changes from other transactions BEGIN; MATCH (p:Product {sku: $sku}) RETURN p.quantity; COMMIT; </code></pre></div>Snapshot Isolation: See consistent snapshot from transaction start <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">SET TRANSACTION ISOLATION LEVEL SNAPSHOT; BEGIN; -- Transaction sees consistent snapshot, immune to concurrent updates MATCH (account:Account) RETURN sum(account.balance) AS total; -- This sum won't change during transaction, even if balances update COMMIT; </code></pre></div>Serializable: Strongest isolation, prevents all anomalies <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">SET TRANSACTION ISOLATION LEVEL SERIALIZABLE; BEGIN; -- Guaranteed serializable execution MATCH (inventory:Product {sku: $sku}) WHERE inventory.quantity >= $qty SET inventory.quantity = inventory.quantity - $qty; COMMIT; </code></pre></div>Implementation in Geode: Isolation is implemented through Multi-Version Concurrency Control (MVCC) and Serializable Snapshot Isolation (SSI). Each transaction operates on a consistent snapshot, and Geode detects dangerous dependency structures to prevent anomalies. <h4 id="durability-persistence-guarantee" class="position-relative d-flex align-items-center group"> Durability: Persistence Guarantee <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="durability-persistence-guarantee" aria-haspopup="dialog" aria-label="Share link: Durability: Persistence Guarantee"> Share link </button> </h4>Durability guarantees that once a transaction commits, its changes persist even if the system immediately crashes. <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">BEGIN TRANSACTION; INSERT (:CriticalOrder {id: $orderId, amount: $amount}); COMMIT; -- From this point, data survives any failure </code></pre></div>Even if the server crashes one nanosecond after COMMIT returns, the order will still exist after recovery. Implementation in Geode: Durability is achieved through: <ol> <li>Write-Ahead Logging: All changes written to persistent WAL before commit</li> <li>fsync(): Forcing data to physical storage media</li> <li>Checkpointing: Periodic snapshots of database state</li> <li>Replication: Synchronous replication to multiple nodes (in distributed mode)</li> </ol> <h3 id="acid-in-geodes-architecture" class="position-relative d-flex align-items-center group"> ACID in Geode&rsquo;s Architecture <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="acid-in-geodes-architecture" aria-haspopup="dialog" aria-label="Share link: ACID in Geodes Architecture"> Share link </button> </h3> <h4 id="transaction-lifecycle" class="position-relative d-flex align-items-center group"> Transaction Lifecycle <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" aria-haspopup="dialog" aria-label="Share link: Transaction Lifecycle"> Share link </button> </h4><ol> <li>BEGIN: Allocate transaction ID, capture snapshot timestamp</li> <li>Execution: Read data from snapshot, write new versions to WAL</li> <li>Validation: Check constraints, detect conflicts, verify isolation</li> <li>Commit: Flush WAL to disk, make versions visible, return success</li> <li>Cleanup: Garbage collect old versions, update indexes</li> </ol> <h4 id="write-ahead-logging-wal" class="position-relative d-flex align-items-center group"> Write-Ahead Logging (WAL) <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-ahead-logging-wal" aria-haspopup="dialog" aria-label="Share link: Write-Ahead Logging (WAL)"> Share link </button> </h4>Every modification is logged before being applied: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-fallback" data-lang="fallback">WAL Entry Format: [TxID][LSN][Operation][Before Image][After Image][Checksum] Example: [tx-12345][lsn-98765][SET][{balance: 100}][{balance: 200}][crc32] </code></pre></div>On commit, Geode calls <code>fsync()</code> to ensure WAL reaches physical media. Only then does commit return to the client. <h4 id="mvcc-and-isolation" class="position-relative d-flex align-items-center group"> MVCC and 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="mvcc-and-isolation" aria-haspopup="dialog" aria-label="Share link: MVCC and Isolation"> Share link </button> </h4>Geode maintains multiple versions of each data item, timestamped with transaction IDs. This allows: <ul> <li>Readers to access consistent snapshots without blocking writers</li> <li>Writers to create new versions without blocking readers</li> <li>Time-travel queries to historical states</li> </ul> <h4 id="crash-recovery" class="position-relative d-flex align-items-center group"> Crash Recovery <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="crash-recovery" aria-haspopup="dialog" aria-label="Share link: Crash Recovery"> Share link </button> </h4>On restart after a crash, Geode: <ol> <li>Reads WAL from last checkpoint</li> <li>Identifies incomplete transactions</li> <li>Rolls back uncommitted transactions</li> <li>Replays committed transactions</li> <li>Rebuilds in-memory structures</li> </ol> This guarantees that all committed data is recovered. <h3 id="use-cases-for-acid-transactions" class="position-relative d-flex align-items-center group"> Use Cases for ACID 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="use-cases-for-acid-transactions" aria-haspopup="dialog" aria-label="Share link: Use Cases for ACID Transactions"> Share link </button> </h3> <h4 id="financial-systems" class="position-relative d-flex align-items-center group"> Financial Systems <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-systems" aria-haspopup="dialog" aria-label="Share link: Financial Systems"> Share link </button> </h4>Banking, trading, and payment processing require absolute correctness: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Multi-party atomic transfer BEGIN TRANSACTION ISOLATION LEVEL SERIALIZABLE; MATCH (account1:Account {id: $account1}) WHERE account1.balance >= $amount1 SET account1.balance = account1.balance - $amount1; MATCH (account2:Account {id: $account2}) WHERE account2.balance >= $amount2 SET account2.balance = account2.balance - $amount2; MATCH (account3:Account {id: $account3}) SET account3.balance = account3.balance + $amount1 + $amount2; INSERT (:Transaction { id: $txId, timestamp: now(), accounts: [$account1, $account2, $account3], amounts: [$amount1, $amount2] }); COMMIT; </code></pre></div>ACID guarantees no money is created or destroyed, even with concurrent transactions or failures. <h4 id="e-commerce" class="position-relative d-flex align-items-center group"> E-Commerce <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="e-commerce" aria-haspopup="dialog" aria-label="Share link: E-Commerce"> Share link </button> </h4>Order processing, inventory management, and payment processing: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">BEGIN TRANSACTION ISOLATION LEVEL SERIALIZABLE; -- Check inventory MATCH (product:Product {sku: $sku}) WHERE product.quantity >= $orderQty SET product.quantity = product.quantity - $orderQty; -- Create order INSERT (order:Order { id: $orderId, customer: $customerId, total: $total, timestamp: now() }); -- Create line items INSERT (order)-[:CONTAINS]->(:LineItem { product: $sku, quantity: $orderQty, price: $price }); -- Process payment INSERT (order)-[:PAID_BY]->(:Payment { method: $paymentMethod, amount: $total, status: 'COMPLETED' }); COMMIT; </code></pre></div>ACID prevents overselling, duplicate orders, and payment inconsistencies. <h4 id="healthcare-records" class="position-relative d-flex align-items-center group"> Healthcare Records <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="healthcare-records" aria-haspopup="dialog" aria-label="Share link: Healthcare Records"> Share link </button> </h4>Medical records require strict consistency and audit trails: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">BEGIN TRANSACTION ISOLATION LEVEL SERIALIZABLE; -- Update patient record MATCH (patient:Patient {mrn: $mrn}) SET patient.lastVisit = now(), patient.primaryPhysician = $physicianId; -- Add diagnosis INSERT (patient)-[:DIAGNOSED_WITH { date: now(), physician: $physicianId, icd10: $icd10Code }]->(:Condition {name: $conditionName}); -- Log access for HIPAA compliance INSERT (:AuditLog { timestamp: now(), user: $userId, action: 'UPDATE_PATIENT_RECORD', patient: $mrn }); COMMIT; </code></pre></div>ACID ensures medical records remain consistent and auditable. <h3 id="best-practices" class="position-relative d-flex align-items-center group"> Best Practices <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" aria-haspopup="dialog" aria-label="Share link: Best Practices"> Share link </button> </h3> <h4 id="transaction-boundaries" class="position-relative d-flex align-items-center group"> Transaction Boundaries <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-boundaries" aria-haspopup="dialog" aria-label="Share link: Transaction Boundaries"> Share link </button> </h4>Keep transactions as short as possible: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Good: Focused transaction BEGIN; MATCH (inventory:Product {sku: $sku}) SET inventory.quantity = inventory.quantity - 1; COMMIT; -- Bad: Long-running transaction holding locks BEGIN; -- Complex calculations... -- External API calls... -- Batch processing... MATCH (inventory:Product {sku: $sku}) SET inventory.quantity = inventory.quantity - 1; COMMIT; </code></pre></div> <h4 id="error-handling" class="position-relative d-flex align-items-center group"> Error Handling <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="error-handling" aria-haspopup="dialog" aria-label="Share link: Error Handling"> Share link </button> </h4>Always handle transaction errors: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-python" data-lang="python">try: with db.transaction(): db.execute("MATCH (p:Product {sku: $sku}) SET p.quantity = p.quantity - 1", sku=sku) db.execute("INSERT (:Order {sku: $sku})", sku=sku) except ConstraintViolation as e: logger.error(f"Constraint violated: {e}") raise except SerializationFailure as e: logger.warn(f"Conflict detected, retrying: {e}") # Implement retry with exponential backoff except Exception as e: logger.error(f"Transaction failed: {e}") raise </code></pre></div> <h4 id="choosing-isolation-levels" class="position-relative d-flex align-items-center group"> Choosing 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="choosing-isolation-levels" aria-haspopup="dialog" aria-label="Share link: Choosing Isolation Levels"> Share link </button> </h4>Select the appropriate isolation level: <ul> <li>Read Committed: Fast, suitable for read-heavy workloads, tolerant of non-repeatable reads</li> <li>Snapshot Isolation: Good balance of performance and consistency</li> <li>Serializable: Use when absolute correctness is required</li> </ul> <h4 id="idempotency" class="position-relative d-flex align-items-center group"> Idempotency <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="idempotency" aria-haspopup="dialog" aria-label="Share link: Idempotency"> Share link </button> </h4>Design operations to be idempotent when possible: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Idempotent: Can safely retry MERGE (user:User {email: $email}) SET user.lastLogin = now(); -- Not idempotent: Creates duplicates on retry INSERT (:User {email: $email}); </code></pre></div> <h4 id="batch-operations" class="position-relative d-flex align-items-center group"> Batch Operations <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" aria-haspopup="dialog" aria-label="Share link: Batch Operations"> Share link </button> </h4>Use batch operations to reduce transaction overhead: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">BEGIN; UNWIND $batch AS item MATCH (product:Product {sku: item.sku}) SET product.quantity = product.quantity - item.qty; COMMIT; </code></pre></div> <h3 id="monitoring-and-troubleshooting" class="position-relative d-flex align-items-center group"> Monitoring and Troubleshooting <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-and-troubleshooting" aria-haspopup="dialog" aria-label="Share link: Monitoring and Troubleshooting"> Share link </button> </h3> <h4 id="transaction-metrics" class="position-relative d-flex align-items-center group"> Transaction Metrics <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" aria-haspopup="dialog" aria-label="Share link: Transaction Metrics"> Share link </button> </h4>Monitor key ACID metrics: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Active transactions CALL dbms.monitor.transactions.active() YIELD txid, duration, isolation; -- Transaction abort rate CALL dbms.monitor.transactions.aborted() YIELD count, reason; -- WAL metrics CALL dbms.monitor.wal.stats() YIELD size, flush_rate, checkpoint_interval; -- Durability lag CALL dbms.monitor.durability.lag() YIELD seconds; </code></pre></div> <h4 id="common-issues" class="position-relative d-flex align-items-center group"> 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="common-issues" aria-haspopup="dialog" aria-label="Share link: Common Issues"> Share link </button> </h4>Transaction Conflicts: High abort rates <ul> <li>Reduce transaction duration</li> <li>Use lower isolation level if acceptable</li> <li>Partition hot data</li> </ul> WAL Growth: Unbounded WAL files <ul> <li>Increase checkpoint frequency</li> <li>Reduce transaction size</li> <li>Check for long-running transactions</li> </ul> Slow Commits: High commit latency <ul> <li>Check disk I/O performance</li> <li>Tune fsync settings</li> <li>Use SSDs for WAL storage</li> </ul> <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/transactions/" >Transactions</a> - Transaction management</li> <li><a href="/tags/isolation/" >Isolation Levels</a> - Isolation guarantees</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><ul> <li><a href="/docs/transactions/" >Transaction Guide</a> - Complete transaction documentation</li> <li><a href="/docs/architecture/" >Architecture Overview</a> - System architecture</li> </ul> Geode’s full ACID implementation ensures your graph data remains consistent, reliable, and durable—essential for production applications where correctness cannot be compromised.

Popular

Related Articles

Transactions and Data Integrity

Transaction Management Guide