Graph Modeling

Graph modeling is the foundational practice of designing how data is structured, connected, and queried in a graph database. In Geode, effective graph modeling determines query performance, data integrity, and application scalability. <h3 id="what-is-graph-modeling" class="position-relative d-flex align-items-center group"> What is Graph Modeling? <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="what-is-graph-modeling" aria-haspopup="dialog" aria-label="Share link: What is Graph Modeling?"> 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>Graph modeling involves designing the structure of your graph data by defining: <ul> <li>Nodes (vertices): Entities representing real-world objects (users, products, locations)</li> <li>Relationships (edges): Connections between nodes with semantic meaning</li> <li>Properties: Key-value pairs storing attributes on nodes and relationships</li> <li>Labels: Categories or types that classify nodes and relationships</li> <li>Constraints: Rules ensuring data integrity and uniqueness</li> </ul> Unlike relational modeling with normalized tables, graph modeling emphasizes connections as first-class citizens. This paradigm shift enables natural representation of highly connected data with complex relationship patterns. <h3 id="core-modeling-concepts" class="position-relative d-flex align-items-center group"> Core Modeling 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-modeling-concepts" aria-haspopup="dialog" aria-label="Share link: Core Modeling Concepts"> Share link </button> </h3> <h4 id="property-graph-model" class="position-relative d-flex align-items-center group"> Property Graph Model <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="property-graph-model" aria-haspopup="dialog" aria-label="Share link: Property Graph Model"> Share link </button> </h4>Geode implements the ISO/IEC 39075:2024 property graph model, where both nodes and relationships can have properties: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">// Node with properties CREATE (:Person {name: 'Alice', age: 30, email: 'alice@example.com'}) // Relationship with properties MATCH (a:Person {name: 'Alice'}), (b:Person {name: 'Bob'}) CREATE (a)-[:KNOWS {since: 2020, strength: 0.8}]->(b) </code></pre></div> <h4 id="node-design-patterns" class="position-relative d-flex align-items-center group"> Node Design 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="node-design-patterns" aria-haspopup="dialog" aria-label="Share link: Node Design Patterns"> Share link </button> </h4>Single vs. Multiple Labels: Nodes can have multiple labels representing different facets: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">// Single label CREATE (:User {id: 1, name: 'Alice'}) // Multiple labels (composite type) CREATE (:User:Admin:Verified {id: 1, name: 'Alice'}) </code></pre></div>Property Selection: Choose properties that support your query patterns: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">// Good: properties support common queries CREATE (:Product { sku: 'PROD-123', name: 'Laptop', category: 'Electronics', price: 999.99, in_stock: true, created_at: datetime('2024-01-15T10:30:00Z') }) // Avoid: redundant computed properties // Instead compute on query or use functions </code></pre></div> <h4 id="relationship-design-patterns" class="position-relative d-flex align-items-center group"> Relationship Design 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="relationship-design-patterns" aria-haspopup="dialog" aria-label="Share link: Relationship Design Patterns"> Share link </button> </h4>Directional Semantics: Relationships are directed, conveying meaning through direction: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">// Clear directional semantics CREATE (user:User)-[:PURCHASED]->(product:Product) CREATE (user:User)-[:FOLLOWS]->(other:User) CREATE (product:Product)-[:BELONGS_TO]->(category:Category) </code></pre></div>Relationship Properties: Store metadata about connections: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">// Temporal relationships CREATE (u:User)-[:VISITED {timestamp: datetime(), duration_ms: 4500}]->(p:Page) // Weighted relationships CREATE (u1:User)-[:SIMILAR_TO {score: 0.85, method: 'collaborative'}]->(u2:User) </code></pre></div>Avoiding Anti-Patterns: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">// Anti-pattern: Dense nodes (hub problem) // Don't create single nodes with millions of relationships // Instead, use intermediate nodes or time-based partitioning // Better: Partition by time CREATE (u:User)-[:PURCHASED]->(o:Order {date: '2024-01'})-[:CONTAINS]->(p:Product) </code></pre></div> <h3 id="schema-design-strategies" class="position-relative d-flex align-items-center group"> Schema Design Strategies <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="schema-design-strategies" aria-haspopup="dialog" aria-label="Share link: Schema Design Strategies"> Share link </button> </h3> <h4 id="schema-first-vs-schema-less" class="position-relative d-flex align-items-center group"> Schema-First vs. Schema-Less <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="schema-first-vs-schema-less" aria-haspopup="dialog" aria-label="Share link: Schema-First vs. Schema-Less"> Share link </button> </h4>Geode supports both approaches: Schema-First (recommended for production): <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">// Define node types with constraints CREATE CONSTRAINT ON (u:User) ASSERT u.id IS UNIQUE; CREATE CONSTRAINT ON (u:User) ASSERT u.email IS UNIQUE; CREATE INDEX FOR (u:User) ON (u.name); </code></pre></div>Schema-Less (flexible for rapid prototyping): <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">// Add properties dynamically CREATE (:DynamicNode {anything: 'goes', schema: 'evolves'}) </code></pre></div> <h4 id="normalization-vs-denormalization" class="position-relative d-flex align-items-center group"> Normalization vs. Denormalization <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="normalization-vs-denormalization" aria-haspopup="dialog" aria-label="Share link: Normalization vs. Denormalization"> Share link </button> </h4>Normalize for Consistency: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">// Normalized: separate node for address CREATE (u:User {name: 'Alice'}) CREATE (a:Address {street: '123 Main', city: 'NYC', zip: '10001'}) CREATE (u)-[:LIVES_AT]->(a) </code></pre></div>Denormalize for Performance: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">// Denormalized: embed address in user CREATE (:User { name: 'Alice', street: '123 Main', city: 'NYC', zip: '10001' }) </code></pre></div>Trade-offs: normalization reduces duplication and maintains consistency; denormalization improves query speed by reducing traversals. <h4 id="temporal-modeling" class="position-relative d-flex align-items-center group"> Temporal Modeling <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="temporal-modeling" aria-haspopup="dialog" aria-label="Share link: Temporal Modeling"> Share link </button> </h4>Model time-varying data with versioned nodes or time-based relationships: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">// Version-based modeling CREATE (u:User {id: 1, name: 'Alice', version: 1, valid_from: datetime()}) // Event-based modeling CREATE (u:User)-[:HAS_EVENT]->(e:Event { type: 'address_change', timestamp: datetime(), old_city: 'NYC', new_city: 'SF' }) </code></pre></div> <h3 id="modeling-for-performance" class="position-relative d-flex align-items-center group"> Modeling for 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="modeling-for-performance" aria-haspopup="dialog" aria-label="Share link: Modeling for Performance"> Share link </button> </h3> <h4 id="index-strategy" class="position-relative d-flex align-items-center group"> Index Strategy <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="index-strategy" aria-haspopup="dialog" aria-label="Share link: Index Strategy"> Share link </button> </h4>Identify access patterns and create indexes: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">// Frequently filtered properties CREATE INDEX FOR (p:Product) ON (p.category); CREATE INDEX FOR (p:Product) ON (p.price); // Compound indexes for multi-property queries CREATE INDEX FOR (u:User) ON (u.last_name, u.first_name); </code></pre></div> <h4 id="relationship-cardinality" class="position-relative d-flex align-items-center group"> Relationship Cardinality <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="relationship-cardinality" aria-haspopup="dialog" aria-label="Share link: Relationship Cardinality"> Share link </button> </h4>Design relationships based on expected cardinality: <ul> <li>One-to-One: User → Profile (direct relationship)</li> <li>One-to-Many: User → Orders (multiple relationships from one node)</li> <li>Many-to-Many: Users → Groups (relationships in both directions)</li> </ul> High-cardinality relationships may require intermediate nodes: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">// Instead of millions of direct relationships // User -[:LIKED]-> millions of Posts // Use intermediate aggregation User -[:HAS_ACTIVITY]-> Activity -[:INCLUDES]-> Posts </code></pre></div> <h3 id="advanced-modeling-patterns" class="position-relative d-flex align-items-center group"> Advanced Modeling 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-modeling-patterns" aria-haspopup="dialog" aria-label="Share link: Advanced Modeling Patterns"> Share link </button> </h3> <h4 id="hypergraphs-and-meta-relationships" class="position-relative d-flex align-items-center group"> Hypergraphs and Meta-Relationships <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="hypergraphs-and-meta-relationships" aria-haspopup="dialog" aria-label="Share link: Hypergraphs and Meta-Relationships"> Share link </button> </h4>Model relationships between relationships: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">// Relationship as a node (reification) CREATE (u1:User)-[:PARTICIPATED]->(r:Relationship {type: 'collaboration'})<-[:PARTICIPATED]-(u2:User) CREATE (r)-[:RESULTED_IN]->(p:Project) </code></pre></div> <h4 id="multi-tenancy" class="position-relative d-flex align-items-center group"> Multi-Tenancy <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="multi-tenancy" aria-haspopup="dialog" aria-label="Share link: Multi-Tenancy"> Share link </button> </h4>Isolate data by tenant: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">// Tenant-scoped nodes CREATE (:User {tenant_id: 'acme', email: 'user@acme.com'}) CREATE (:User {tenant_id: 'globex', email: 'user@globex.com'}) // Enforce with Row-Level Security CREATE POLICY tenant_isolation ON User USING (tenant_id = current_setting('app.tenant_id')) </code></pre></div> <h4 id="hierarchies-and-trees" class="position-relative d-flex align-items-center group"> Hierarchies and Trees <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="hierarchies-and-trees" aria-haspopup="dialog" aria-label="Share link: Hierarchies and Trees"> Share link </button> </h4>Model hierarchical data: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">// Parent-child relationships CREATE (root:Category {name: 'Electronics'}) CREATE (sub:Category {name: 'Laptops'}) CREATE (root)-[:HAS_SUBCATEGORY]->(sub) // Materialized paths for fast traversal CREATE (:Category {name: 'Laptops', path: '/Electronics/Computers/Laptops'}) </code></pre></div> <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><ol> <li>Model for Your Queries: Design based on how data will be accessed, not just how it’s structured</li> <li>Use Meaningful Labels: Choose descriptive, singular nouns (<code>:User</code>, <code>:Product</code>, not <code>:Users</code> or <code>:user</code>)</li> <li>Relationship Types as Verbs: Name relationships as actions (<code>:PURCHASED</code>, <code>:FOLLOWS</code>, <code>:CONTAINS</code>)</li> <li>Constrain Early: Define uniqueness and existence constraints during design, not as an afterthought</li> <li>Property Naming: Use snake_case or camelCase consistently across the schema</li> <li>Avoid Graph Anti-Patterns: Dense nodes, properties as relationships, relationship overloading</li> <li>Version Your Schema: Track schema changes with migration scripts and version metadata</li> <li>Test with Production Scale: Validate model performance with realistic data volumes</li> </ol> <h3 id="modeling-tools-and-workflow" class="position-relative d-flex align-items-center group"> Modeling Tools and Workflow <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="modeling-tools-and-workflow" aria-haspopup="dialog" aria-label="Share link: Modeling Tools and Workflow"> Share link </button> </h3> <h4 id="python-client-modeling" class="position-relative d-flex align-items-center group"> Python Client Modeling <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="python-client-modeling" aria-haspopup="dialog" aria-label="Share link: Python Client Modeling"> Share link </button> </h4><div class="highlight"><pre tabindex="0" class="chroma"><code class="language-python" data-lang="python">from geode_client import Client client = Client(host="localhost", port=3141) async with client.connection() as conn: # Define schema with constraints await conn.query(""" CREATE CONSTRAINT ON (u:User) ASSERT u.id IS UNIQUE; CREATE INDEX FOR (u:User) ON (u.email); """) # Insert modeled data await conn.query(""" CREATE (u:User {id: $id, email: $email, created_at: datetime()}) """, {"id": 1, "email": "[email protected]"}) </code></pre></div> <h4 id="go-client-modeling" class="position-relative d-flex align-items-center group"> Go Client Modeling <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="go-client-modeling" aria-haspopup="dialog" aria-label="Share link: Go Client Modeling"> Share link </button> </h4><div class="highlight"><pre tabindex="0" class="chroma"><code class="language-go" data-lang="go">db, _ := sql.Open("geode", "quic://localhost:3141") // Schema definition _, err := db.Exec(` CREATE CONSTRAINT ON (p:Product) ASSERT p.sku IS UNIQUE; CREATE INDEX FOR (p:Product) ON (p.category); `) // Insert with prepared statement stmt, _ := db.Prepare("CREATE (:Product {sku: $1, name: $2, price: $3})") stmt.Exec("PROD-123", "Laptop", 999.99) </code></pre></div> <h4 id="rust-client-modeling" class="position-relative d-flex align-items-center group"> Rust Client Modeling <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="rust-client-modeling" aria-haspopup="dialog" aria-label="Share link: Rust Client Modeling"> Share link </button> </h4><div class="highlight"><pre tabindex="0" class="chroma"><code class="language-rust" data-lang="rust">use geode_client::Client; let client = Client::from_dsn("localhost:3141")?; let mut conn = client.connect().await?; // Define relationships with properties let _ = conn.query(r#" CREATE (u:User {id: 1})-[:PLACED {timestamp: datetime()}]->(o:Order {total: 99.99}) "#).await?; </code></pre></div> <h3 id="common-modeling-mistakes" class="position-relative d-flex align-items-center group"> Common Modeling Mistakes <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-modeling-mistakes" aria-haspopup="dialog" aria-label="Share link: Common Modeling Mistakes"> Share link </button> </h3><ol> <li>Over-Denormalization: Embedding everything in single nodes, losing relationship semantics</li> <li>Under-Indexing: Not creating indexes on frequently queried properties</li> <li>Property Soup: Adding every possible attribute without considering query patterns</li> <li>Relationship Overloading: Using single relationship type for multiple semantic meanings</li> <li>Ignoring Cardinality: Not accounting for high-cardinality relationships causing dense nodes</li> <li>No Schema Evolution Plan: Making schema changes without backward compatibility strategy</li> </ol> <h3 id="migration-and-evolution" class="position-relative d-flex align-items-center group"> Migration and Evolution <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="migration-and-evolution" aria-haspopup="dialog" aria-label="Share link: Migration and Evolution"> Share link </button> </h3>Handle schema changes gracefully: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">// Add new property with default MATCH (u:User) SET u.status = COALESCE(u.status, 'active') // Add new label to existing nodes MATCH (u:User) WHERE u.is_admin = true SET u:Admin // Migrate relationship properties MATCH (u:User)-[r:KNOWS]->(v:User) SET r.migrated_at = datetime() </code></pre></div> <h3 id="performance-testing" class="position-relative d-flex align-items-center group"> Performance Testing <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-testing" aria-haspopup="dialog" aria-label="Share link: Performance Testing"> Share link </button> </h3>Validate your model with realistic queries: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-python" data-lang="python"># Test query performance start = time.time() result, _ = await client.query(""" MATCH (u:User)-[:PURCHASED]->(p:Product) WHERE p.category = 'Electronics' RETURN u.name, COUNT(p) AS purchases ORDER BY purchases DESC LIMIT 10 """) elapsed = time.time() - start print(f"Query took {elapsed:.2f}s, returned {len(result.rows)} rows") </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>Graph Algorithms: Leverage your model with pathfinding, centrality, and community detection</li> <li>Query Optimization: Optimize GQL queries based on your schema design</li> <li>Indexing: Create appropriate indexes for your access patterns</li> <li>Transactions: Ensure data consistency when modifying your graph</li> <li>Security: Implement Row-Level Security policies based on your data model</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="/tags/types/" >GQL Data Types</a> - Understand available property types</li> <li><a href="/tags/indexing/" >Indexing Strategies</a> - Optimize query performance</li> <li><a href="/tags/performance/" >Query Performance</a> - Performance tuning techniques</li> <li><a href="/tags/gql-reference/" >GQL Reference</a> - Complete language reference</li> <li><a href="/tags/transactions/" >Transaction Management</a> - Ensure data integrity</li> </ul> Graph modeling is both an art and science. Start with a clear understanding of your domain, iterate based on query patterns, and continuously validate with realistic workloads to achieve optimal performance and maintainability. <h3 id="domain-driven-graph-modeling" class="position-relative d-flex align-items-center group"> Domain-Driven Graph Modeling <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="domain-driven-graph-modeling" aria-haspopup="dialog" aria-label="Share link: Domain-Driven Graph Modeling"> Share link </button> </h3> <h4 id="social-network-example" class="position-relative d-flex align-items-center group"> Social Network 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="social-network-example" aria-haspopup="dialog" aria-label="Share link: Social Network Example"> Share link </button> </h4>Model a social network with rich relationship semantics: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Core entities CREATE (:User { id: INTEGER, username: STRING, email: STRING, bio: TEXT, joined_at: TIMESTAMP, last_active: TIMESTAMP }) CREATE (:Post { id: INTEGER, content: TEXT, created_at: TIMESTAMP, edited_at: TIMESTAMP, visibility: STRING -- 'public', 'friends', 'private' }) CREATE (:Comment { id: INTEGER, content: TEXT, created_at: TIMESTAMP }) -- Relationships with properties CREATE (u1:User)-[:FOLLOWS { since: TIMESTAMP, notification_enabled: BOOLEAN }]->(u2:User) CREATE (u:User)-[:POSTED { posted_at: TIMESTAMP }]->(p:Post) CREATE (u:User)-[:LIKED { liked_at: TIMESTAMP, reaction_type: STRING -- 'like', 'love', 'laugh', etc. }]->(p:Post) CREATE (u:User)-[:COMMENTED { commented_at: TIMESTAMP }]->(c:Comment)-[:ON]->(p:Post) -- Constraints CREATE CONSTRAINT ON (u:User) ASSERT u.id IS UNIQUE; CREATE CONSTRAINT ON (u:User) ASSERT u.email IS UNIQUE; CREATE CONSTRAINT ON (p:Post) ASSERT p.id IS UNIQUE; -- Indexes for common queries CREATE INDEX FOR (u:User) ON (u.username); CREATE INDEX FOR (p:Post) ON (p.created_at); CREATE INDEX FOR (u:User) ON (u.last_active); </code></pre></div>Common query patterns: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- User feed: posts from followed users MATCH (me:User {id: $my_id})-[:FOLLOWS]->(friend:User) MATCH (friend)-[:POSTED]->(post:Post) WHERE post.created_at > datetime().minusDays(7) RETURN post, friend.username ORDER BY post.created_at DESC LIMIT 50 -- Friend recommendations: friends of friends MATCH (me:User {id: $my_id})-[:FOLLOWS]->()-[:FOLLOWS]->(suggestion:User) WHERE NOT (me)-[:FOLLOWS]->(suggestion) AND suggestion.id != $my_id WITH suggestion, COUNT(*) AS mutual_friends ORDER BY mutual_friends DESC LIMIT 10 RETURN suggestion, mutual_friends -- Trending posts: high engagement recently MATCH (p:Post) WHERE p.created_at > datetime().minusHours(24) WITH p, COUNT{(p)<-[:LIKED]-()} AS likes, COUNT{(p)<-[:ON]-(c:Comment)} AS comments WITH p, (likes * 1.0 + comments * 2.0) AS engagement_score ORDER BY engagement_score DESC LIMIT 20 RETURN p, engagement_score </code></pre></div> <h4 id="e-commerce-platform" class="position-relative d-flex align-items-center group"> E-Commerce Platform <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-platform" aria-haspopup="dialog" aria-label="Share link: E-Commerce Platform"> Share link </button> </h4>Model products, inventory, and orders: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Product catalog CREATE (:Product { sku: STRING, name: STRING, description: TEXT, price: DECIMAL, currency: STRING, stock_quantity: INTEGER, reorder_point: INTEGER, discontinued: BOOLEAN }) CREATE (:Category { id: INTEGER, name: STRING, slug: STRING, parent_id: INTEGER -- Self-referential hierarchy }) CREATE (:Brand { id: INTEGER, name: STRING, logo_url: STRING }) -- Relationships CREATE (p:Product)-[:IN_CATEGORY]->(c:Category) CREATE (p:Product)-[:MADE_BY]->(b:Brand) CREATE (p1:Product)-[:SIMILAR_TO { similarity_score: FLOAT, algorithm: STRING }]->(p2:Product) -- Orders and customers CREATE (:Customer { id: INTEGER, email: STRING, name: STRING, lifetime_value: DECIMAL }) CREATE (:Order { id: INTEGER, order_number: STRING, status: STRING, -- 'pending', 'confirmed', 'shipped', 'delivered' total: DECIMAL, created_at: TIMESTAMP, shipped_at: TIMESTAMP, delivered_at: TIMESTAMP }) CREATE (:OrderItem { quantity: INTEGER, unit_price: DECIMAL, discount: DECIMAL }) -- Order relationships CREATE (c:Customer)-[:PLACED]->(o:Order) CREATE (o:Order)-[:CONTAINS]->(item:OrderItem)-[:OF_PRODUCT]->(p:Product) -- Indexes for e-commerce queries CREATE INDEX FOR (p:Product) ON (p.sku); CREATE INDEX FOR (p:Product) ON (p.price); CREATE INDEX FOR (p:Product) ON (p.stock_quantity); CREATE INDEX FOR (o:Order) ON (o.status); CREATE INDEX FOR (o:Order) ON (o.created_at); </code></pre></div>E-commerce query patterns: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Product search with filters MATCH (p:Product)-[:IN_CATEGORY]->(c:Category) WHERE p.price BETWEEN $min_price AND $max_price AND c.slug = $category AND p.stock_quantity > 0 AND p.discontinued = false RETURN p ORDER BY p.popularity_score DESC LIMIT 24 -- Shopping cart recommendations MATCH (cart_product:Product {id IN $cart_product_ids}) MATCH (cart_product)-[:SIMILAR_TO]->(rec:Product) WHERE NOT rec.id IN $cart_product_ids AND rec.stock_quantity > 0 WITH rec, AVG(similarity_score) AS avg_similarity ORDER BY avg_similarity DESC LIMIT 10 RETURN rec -- Inventory reordering MATCH (p:Product) WHERE p.stock_quantity <= p.reorder_point AND p.discontinued = false WITH p, p.reorder_point + 100 AS reorder_quantity RETURN p.sku, p.name, p.stock_quantity, reorder_quantity ORDER BY p.stock_quantity ASC </code></pre></div> <h3 id="advanced-modeling-patterns-1" class="position-relative d-flex align-items-center group"> Advanced Modeling 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-modeling-patterns-1" aria-haspopup="dialog" aria-label="Share link: Advanced Modeling Patterns"> Share link </button> </h3> <h4 id="graph-versioning" class="position-relative d-flex align-items-center group"> Graph Versioning <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="graph-versioning" aria-haspopup="dialog" aria-label="Share link: Graph Versioning"> Share link </button> </h4>Track changes over time: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Version-aware entities CREATE (:Document { id: INTEGER, version: INTEGER, content: TEXT, valid_from: TIMESTAMP, valid_to: TIMESTAMP, is_current: BOOLEAN }) -- Version chain CREATE (doc_v1:Document {id: 1, version: 1, valid_from: '2024-01-01T00:00:00Z'}) CREATE (doc_v2:Document {id: 1, version: 2, valid_from: '2024-01-15T10:30:00Z'}) CREATE (doc_v1)-[:NEXT_VERSION]->(doc_v2) -- Query specific version MATCH (d:Document {id: $doc_id}) WHERE d.valid_from <= $timestamp AND (d.valid_to IS NULL OR d.valid_to > $timestamp) RETURN d -- Query current version MATCH (d:Document {id: $doc_id, is_current: true}) RETURN d </code></pre></div> <h4 id="bipartite-graphs" class="position-relative d-flex align-items-center group"> Bipartite Graphs <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="bipartite-graphs" aria-haspopup="dialog" aria-label="Share link: Bipartite Graphs"> Share link </button> </h4>Model two distinct node types with relationships: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Users and movies (recommendation system) CREATE (:User {id: INTEGER, name: STRING}) CREATE (:Movie {id: INTEGER, title: STRING, genre: STRING}) CREATE (u:User)-[:RATED { rating: FLOAT, -- 1.0 to 5.0 timestamp: TIMESTAMP }]->(m:Movie) -- Collaborative filtering query MATCH (me:User {id: $my_id})-[r1:RATED]->(m:Movie)<-[r2:RATED]-(similar:User) WHERE ABS(r1.rating - r2.rating) < 1.0 -- Similar ratings WITH similar, COUNT(m) AS common_movies ORDER BY common_movies DESC LIMIT 10 MATCH (similar)-[r:RATED]->(rec:Movie) WHERE NOT (me)-[:RATED]->(rec) AND r.rating >= 4.0 RETURN rec.title, AVG(r.rating) AS avg_rating ORDER BY avg_rating DESC LIMIT 20 </code></pre></div> <h4 id="knowledge-graphs" class="position-relative d-flex align-items-center group"> Knowledge Graphs <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="knowledge-graphs" aria-haspopup="dialog" aria-label="Share link: Knowledge Graphs"> Share link </button> </h4>Model entities and semantic relationships: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Entities with types CREATE (:Entity { id: STRING, name: STRING, type: STRING, -- 'person', 'organization', 'location', 'event' description: TEXT }) -- Semantic relationships CREATE (e1:Entity)-[:WORKED_AT { from_date: DATE, to_date: DATE, role: STRING }]->(e2:Entity) CREATE (e1:Entity)-[:LOCATED_IN]->(e2:Entity) CREATE (e1:Entity)-[:FOUNDED {founding_date: DATE}]->(e2:Entity) -- Knowledge graph queries MATCH path = (person:Entity {type: 'person', name: 'Alice'}) -[:WORKED_AT*1..2]-> (company:Entity {type: 'organization'}) RETURN path -- Find connections between entities MATCH path = shortestPath( (e1:Entity {name: 'Alice'})-[*..5]-(e2:Entity {name: 'Bob'}) ) RETURN path, LENGTH(path) AS degree_of_separation </code></pre></div> <h4 id="geospatial-modeling" class="position-relative d-flex align-items-center group"> Geospatial Modeling <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="geospatial-modeling" aria-haspopup="dialog" aria-label="Share link: Geospatial Modeling"> Share link </button> </h4>Model location-based data: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Locations with coordinates CREATE (:Place { id: INTEGER, name: STRING, latitude: FLOAT, longitude: FLOAT, category: STRING -- 'restaurant', 'hotel', 'attraction' }) -- Spatial index (for distance queries) CREATE SPATIAL INDEX FOR (p:Place) ON (p.latitude, p.longitude); -- Distance-based queries MATCH (p:Place) WHERE distance( point({latitude: p.latitude, longitude: p.longitude}), point({latitude: $my_lat, longitude: $my_lon}) ) < $radius_meters AND p.category = 'restaurant' RETURN p, distance(...) AS distance_m ORDER BY distance_m LIMIT 10 </code></pre></div> <h3 id="performance-modeling" class="position-relative d-flex align-items-center group"> Performance Modeling <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-modeling" aria-haspopup="dialog" aria-label="Share link: Performance Modeling"> Share link </button> </h3> <h4 id="hotspot-avoidance" class="position-relative d-flex align-items-center group"> Hotspot Avoidance <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="hotspot-avoidance" aria-haspopup="dialog" aria-label="Share link: Hotspot Avoidance"> Share link </button> </h4>Prevent dense nodes (supernodes): <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- BAD: Single popular user with millions of followers (:User {id: 'celebrity'})<-[:FOLLOWS]-(:User) [x1,000,000] -- GOOD: Partition followers by time (:User {id: 'celebrity'}) <-[:MANAGED_BY]-(:FollowerList {period: '2024-01'}) <-[:IN_LIST]-(:User) [x100,000] (:User {id: 'celebrity'}) <-[:MANAGED_BY]-(:FollowerList {period: '2024-02'}) <-[:IN_LIST]-(:User) [x100,000] -- Query pattern MATCH (celebrity:User {id: $celebrity_id}) <-[:MANAGED_BY]-(list:FollowerList) <-[:IN_LIST]-(follower:User) WHERE list.period >= $start_period RETURN follower </code></pre></div> <h4 id="materialized-aggregations" class="position-relative d-flex align-items-center group"> Materialized Aggregations <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="materialized-aggregations" aria-haspopup="dialog" aria-label="Share link: Materialized Aggregations"> Share link </button> </h4>Pre-compute expensive aggregations: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Expensive query (computed on-demand) MATCH (u:User {id: $user_id})-[:POSTED]->(p:Post) RETURN u, COUNT(p) AS post_count -- Better: Maintain denormalized count CREATE (:User { id: INTEGER, post_count: INTEGER -- Updated by trigger }) -- Trigger keeps count in sync CREATE TRIGGER maintain_post_count AFTER INSERT OR DELETE ON [:POSTED] FOR EACH RELATIONSHIP EXECUTE GQL MATCH (u:User) WHERE id(u) = id(startNode(COALESCE(NEW, OLD))) SET u.post_count = u.post_count + CASE WHEN INSERTING THEN 1 ELSE -1 END -- Fast query MATCH (u:User {id: $user_id}) RETURN u.post_count </code></pre></div> <h4 id="index-coverage" class="position-relative d-flex align-items-center group"> Index Coverage <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="index-coverage" aria-haspopup="dialog" aria-label="Share link: Index Coverage"> Share link </button> </h4>Design indexes to cover query patterns: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Compound index for multi-property queries CREATE INDEX FOR (p:Product) ON (p.category, p.price, p.stock_quantity); -- This index covers: MATCH (p:Product) WHERE p.category = 'electronics' AND p.price < 1000 AND p.stock_quantity > 0 RETURN p -- Index-only scan, no table lookup needed </code></pre></div> <h3 id="schema-evolution" class="position-relative d-flex align-items-center group"> Schema Evolution <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="schema-evolution" aria-haspopup="dialog" aria-label="Share link: Schema Evolution"> Share link </button> </h3> <h4 id="adding-properties" class="position-relative d-flex align-items-center group"> Adding 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="adding-properties" aria-haspopup="dialog" aria-label="Share link: Adding Properties"> Share link </button> </h4>Add properties with default values: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Add new property to existing nodes MATCH (u:User) WHERE NOT EXISTS(u.email_verified) SET u.email_verified = false -- Or use COALESCE in queries MATCH (u:User) RETURN u.name, COALESCE(u.email_verified, false) AS verified </code></pre></div> <h4 id="migrating-relationships" class="position-relative d-flex align-items-center group"> Migrating Relationships <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="migrating-relationships" aria-haspopup="dialog" aria-label="Share link: Migrating Relationships"> Share link </button> </h4>Change relationship structure: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Old model: direct relationship (u:User)-[:FRIEND]->(f:User) -- New model: relationship as node (to add properties) (u:User)-[:FRIENDSHIP_REQUEST]->(fr:FriendRequest { status: 'accepted', requested_at: TIMESTAMP, accepted_at: TIMESTAMP })<-[:FRIENDSHIP_REQUEST]-(f:User) -- Migration query MATCH (u1:User)-[old:FRIEND]->(u2:User) CREATE (u1)-[:FRIENDSHIP_REQUEST]->(fr:FriendRequest { status: 'accepted', requested_at: old.since, accepted_at: old.since })<-[:FRIENDSHIP_REQUEST]-(u2) DELETE old </code></pre></div> <h4 id="schema-versioning" class="position-relative d-flex align-items-center group"> Schema Versioning <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="schema-versioning" aria-haspopup="dialog" aria-label="Share link: Schema Versioning"> Share link </button> </h4>Track schema changes: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Schema metadata CREATE (:SchemaVersion { version: INTEGER, applied_at: TIMESTAMP, description: TEXT }) -- Migration scripts -- v1_to_v2.gql CREATE CONSTRAINT ON (u:User) ASSERT u.email IS UNIQUE; ALTER LABEL User ADD PROPERTY email_verified BOOLEAN DEFAULT false; INSERT (:SchemaVersion {version: 2, applied_at: datetime(), description: 'Add email verification'}) </code></pre></div> <h3 id="further-reading-1" 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-1" aria-haspopup="dialog" aria-label="Share link: Further Reading"> Share link </button> </h3><ul> <li><a href="/tags/types/" >GQL Data Types</a> - Understand available property types</li> <li><a href="/tags/indexing/" >Indexing Strategies</a> - Optimize query performance</li> <li><a href="/tags/performance/" >Query Performance</a> - Performance tuning techniques</li> <li><a href="/tags/gql-reference/" >GQL Reference</a> - Complete language reference</li> <li><a href="/tags/transactions/" >Transaction Management</a> - Ensure data integrity</li> <li><a href="https://www.oreilly.com/library/view/graph-algorithms/9781492047674/" aria-label="Graph Algorithms for Data Science – opens in new window" target="_blank" rel="noopener noreferrer" >Graph Algorithms for Data Science ↗ </a> </li> <li><a href="https://martinfowler.com/books/nosql.html" aria-label="NoSQL Distilled – opens in new window" target="_blank" rel="noopener noreferrer" >NoSQL Distilled ↗ </a> - Data modeling patterns</li> <li><a href="https://www.oreilly.com/library/view/graph-databases-2nd/9781491930892/" aria-label="Graph Databases – opens in new window" target="_blank" rel="noopener noreferrer" >Graph Databases ↗ </a> - O’Reilly guide</li> </ul> Graph modeling is both an art and science. Start with a clear understanding of your domain, iterate based on query patterns, and continuously validate with realistic workloads to achieve optimal performance and maintainability.

Popular

Related Articles

Graph Modeling Guide

Graph Schema Design Guide