Category: Graph Modeling

The Graph Modeling category covers techniques, patterns, and best practices for designing effective graph database schemas. Learn how to translate your domain into nodes and relationships, optimize for query patterns, and build scalable, maintainable graph data models. <h3 id="introduction-to-graph-modeling" class="position-relative d-flex align-items-center group"> Introduction to 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="introduction-to-graph-modeling" aria-haspopup="dialog" aria-label="Share link: Introduction to 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 is the practice of designing how your application’s data will be represented as nodes, relationships, and properties in a graph database. Unlike relational database design with its normalization rules and table schemas, graph modeling focuses on identifying entities and their connections, emphasizing how data relates rather than how it’s stored. Effective graph modeling makes queries natural and performant, aligns the database structure with your domain model, and enables the database to grow gracefully as requirements evolve. The flexibility of graph databases allows iteration and refinement, but good initial modeling saves significant effort later. <h3 id="fundamental-modeling-principles" class="position-relative d-flex align-items-center group"> Fundamental Modeling Principles <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="fundamental-modeling-principles" aria-haspopup="dialog" aria-label="Share link: Fundamental Modeling Principles"> Share link </button> </h3> <h4 id="nodes-represent-entities" class="position-relative d-flex align-items-center group"> Nodes Represent Entities <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="nodes-represent-entities" aria-haspopup="dialog" aria-label="Share link: Nodes Represent Entities"> Share link </button> </h4>Nodes are the primary entities in your domain: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- People in a social network CREATE (alice:Person { id: 'person_001', name: 'Alice Anderson', email: 'alice@example.com', birthdate: date('1990-05-15'), city: 'New York' }); -- Products in an e-commerce system CREATE (laptop:Product { id: 'prod_123', name: '15" Pro Laptop', sku: 'LAPTOP-PRO-15', price: 1299.99, category: 'Electronics' }); -- Locations in a logistics system CREATE (warehouse:Location { id: 'loc_456', name: 'Central Warehouse', address: '123 Industrial Blvd', lat: 40.7128, lon: -74.0060 }); </code></pre></div>Guideline: Create a node for anything you might want to query independently or that has properties distinct from its relationships. <h4 id="relationships-express-connections" class="position-relative d-flex align-items-center group"> Relationships Express Connections <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="relationships-express-connections" aria-haspopup="dialog" aria-label="Share link: Relationships Express Connections"> Share link </button> </h4>Relationships show how entities connect: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Social connection MATCH (alice:Person {id: 'person_001'}), (bob:Person {id: 'person_002'}) CREATE (alice)-[:FRIENDS_WITH {since: date('2020-01-15'), strength: 0.85}]->(bob); -- Purchase transaction MATCH (customer:Person {id: 'person_001'}), (product:Product {id: 'prod_123'}) CREATE (customer)-[:PURCHASED { date: datetime('2024-03-15T10:30:00'), price: 1299.99, quantity: 1, order_id: 'order_789' }]->(product); -- Geographic relationship MATCH (product:Product {id: 'prod_123'}), (warehouse:Location {id: 'loc_456'}) CREATE (product)-[:STORED_AT {quantity: 50, last_restocked: date('2024-03-01')}]->(warehouse); </code></pre></div>Guideline: Use relationships to express verbs and meaningful connections. Name relationships as actions (PURCHASED, KNOWS, MANAGES) or states (BELONGS_TO, LOCATED_IN). <h4 id="properties-store-attributes" class="position-relative d-flex align-items-center group"> Properties Store Attributes <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="properties-store-attributes" aria-haspopup="dialog" aria-label="Share link: Properties Store Attributes"> Share link </button> </h4>Properties describe nodes and relationships: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Node properties CREATE (alice:Person { name: 'Alice', -- Identity email: 'alice@ex.com', -- Contact age: 30, -- Demographic role: 'Engineer', -- Classification salary: 95000, -- Quantitative active: true, -- Boolean state skills: ['Python', 'Go', 'SQL'], -- Lists preferences: {theme: 'dark', language: 'en'} -- Maps }); -- Relationship properties CREATE (alice)-[:WORKED_ON { start_date: date('2023-01-01'), end_date: date('2023-12-31'), role: 'Lead Developer', hours: 1600, satisfaction: 4.5 }]->(project); </code></pre></div>Guideline: Store properties directly on the entity they describe. Avoid deeply nested structures; flatten when possible. <h3 id="modeling-patterns" class="position-relative d-flex align-items-center group"> 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="modeling-patterns" aria-haspopup="dialog" aria-label="Share link: Modeling Patterns"> Share link </button> </h3> <h4 id="pattern-1-one-to-many-relationships" class="position-relative d-flex align-items-center group"> Pattern 1: One-to-Many 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="pattern-1-one-to-many-relationships" aria-haspopup="dialog" aria-label="Share link: Pattern 1: One-to-Many Relationships"> Share link </button> </h4>Example: Blog posts and comments <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Create author and posts CREATE (author:User {name: 'Alice', email: 'alice@blog.com'}); CREATE (post1:Post { id: 'post_001', title: 'Graph Databases Explained', content: '...', published: datetime('2024-03-01T09:00:00'), views: 1250 }); CREATE (post2:Post { id: 'post_002', title: 'Modeling Best Practices', content: '...', published: datetime('2024-03-15T14:30:00'), views: 890 }); -- Connect author to posts MATCH (a:User {name: 'Alice'}), (p1:Post {id: 'post_001'}) CREATE (a)-[:AUTHORED]->(p1); MATCH (a:User {name: 'Alice'}), (p2:Post {id: 'post_002'}) CREATE (a)-[:AUTHORED]->(p2); -- Query all posts by author MATCH (author:User {name: 'Alice'})-[:AUTHORED]->(post:Post) RETURN post.title, post.published, post.views ORDER BY post.published DESC; </code></pre></div> <h4 id="pattern-2-many-to-many-relationships" class="position-relative d-flex align-items-center group"> Pattern 2: Many-to-Many 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="pattern-2-many-to-many-relationships" aria-haspopup="dialog" aria-label="Share link: Pattern 2: Many-to-Many Relationships"> Share link </button> </h4>Example: Students and courses <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Create students CREATE (alice:Student {id: 'student_001', name: 'Alice'}); CREATE (bob:Student {id: 'student_002', name: 'Bob'}); -- Create courses CREATE (db:Course {id: 'course_101', name: 'Databases', credits: 3}); CREATE (algo:Course {id: 'course_102', name: 'Algorithms', credits: 4}); -- Enrollment relationships with properties MATCH (alice:Student {id: 'student_001'}), (db:Course {id: 'course_101'}) CREATE (alice)-[:ENROLLED_IN { semester: 'Fall 2024', grade: 'A', enrollment_date: date('2024-08-20') }]->(db); MATCH (alice:Student {id: 'student_001'}), (algo:Course {id: 'course_102'}) CREATE (alice)-[:ENROLLED_IN { semester: 'Fall 2024', grade: 'B+', enrollment_date: date('2024-08-20') }]->(algo); MATCH (bob:Student {id: 'student_002'}), (algo:Course {id: 'course_102'}) CREATE (bob)-[:ENROLLED_IN { semester: 'Fall 2024', grade: 'A-', enrollment_date: date('2024-08-21') }]->(algo); -- Query students in a course MATCH (student:Student)-[enrollment:ENROLLED_IN]->(course:Course {id: 'course_102'}) RETURN student.name, enrollment.grade ORDER BY enrollment.grade DESC; </code></pre></div> <h4 id="pattern-3-hierarchical-structures" class="position-relative d-flex align-items-center group"> Pattern 3: Hierarchical Structures <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="pattern-3-hierarchical-structures" aria-haspopup="dialog" aria-label="Share link: Pattern 3: Hierarchical Structures"> Share link </button> </h4>Example: Organizational chart <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Create employees CREATE (ceo:Employee {name: 'Alice', title: 'CEO'}); CREATE (cto:Employee {name: 'Bob', title: 'CTO'}); CREATE (vp_eng:Employee {name: 'Carol', title: 'VP Engineering'}); CREATE (eng1:Employee {name: 'Dave', title: 'Senior Engineer'}); CREATE (eng2:Employee {name: 'Eve', title: 'Engineer'}); -- Create reporting structure MATCH (cto:Employee {name: 'Bob'}), (ceo:Employee {name: 'Alice'}) CREATE (cto)-[:REPORTS_TO]->(ceo); MATCH (vp:Employee {name: 'Carol'}), (cto:Employee {name: 'Bob'}) CREATE (vp)-[:REPORTS_TO]->(cto); MATCH (eng1:Employee {name: 'Dave'}), (vp:Employee {name: 'Carol'}) CREATE (eng1)-[:REPORTS_TO]->(vp); MATCH (eng2:Employee {name: 'Eve'}), (eng1:Employee {name: 'Dave'}) CREATE (eng2)-[:REPORTS_TO]->(eng1); -- Query entire management chain MATCH (employee:Employee {name: 'Eve'})-[:REPORTS_TO*]->(manager:Employee) RETURN manager.name, manager.title ORDER BY length([(employee)-[:REPORTS_TO*]->(manager) | 1]); -- Find all direct and indirect reports MATCH (manager:Employee {name: 'Bob'})<-[:REPORTS_TO*]-(report:Employee) RETURN count(report) as total_reports; </code></pre></div> <h4 id="pattern-4-time-based-modeling" class="position-relative d-flex align-items-center group"> Pattern 4: Time-Based 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="pattern-4-time-based-modeling" aria-haspopup="dialog" aria-label="Share link: Pattern 4: Time-Based Modeling"> Share link </button> </h4>Example: Historical relationships <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Model job history with time-bound relationships CREATE (alice:Person {name: 'Alice'}); CREATE (acme:Company {name: 'Acme Corp'}); CREATE (techco:Company {name: 'TechCo Inc'}); -- Past employment CREATE (alice)-[:WORKED_AT { start_date: date('2018-01-15'), end_date: date('2021-06-30'), title: 'Software Engineer', current: false }]->(acme); -- Current employment CREATE (alice)-[:WORKED_AT { start_date: date('2021-07-01'), end_date: null, title: 'Senior Engineer', current: true }]->(techco); -- Query current employer MATCH (person:Person {name: 'Alice'})-[job:WORKED_AT]->(company:Company) WHERE job.current = true RETURN company.name, job.title; -- Query complete job history MATCH (person:Person {name: 'Alice'})-[job:WORKED_AT]->(company:Company) RETURN company.name, job.title, job.start_date, job.end_date ORDER BY job.start_date DESC; </code></pre></div> <h4 id="pattern-5-intermediate-nodes-for-rich-relationships" class="position-relative d-flex align-items-center group"> Pattern 5: Intermediate Nodes for Rich 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="pattern-5-intermediate-nodes-for-rich-relationships" aria-haspopup="dialog" aria-label="Share link: Pattern 5: Intermediate Nodes for Rich Relationships"> Share link </button> </h4>Example: Complex order system <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Create entities CREATE (customer:Customer {id: 'cust_001', name: 'Alice'}); CREATE (product1:Product {id: 'prod_101', name: 'Laptop', price: 1299.99}); CREATE (product2:Product {id: 'prod_102', name: 'Mouse', price: 29.99}); -- Create order as intermediate node CREATE (order:Order { id: 'order_001', date: datetime('2024-03-15T10:30:00'), status: 'shipped', total: 1329.98 }); -- Connect customer to order MATCH (c:Customer {id: 'cust_001'}), (o:Order {id: 'order_001'}) CREATE (c)-[:PLACED]->(o); -- Connect order to products with line item details MATCH (o:Order {id: 'order_001'}), (p1:Product {id: 'prod_101'}) CREATE (o)-[:CONTAINS {quantity: 1, unit_price: 1299.99, subtotal: 1299.99}]->(p1); MATCH (o:Order {id: 'order_001'}), (p2:Product {id: 'prod_102'}) CREATE (o)-[:CONTAINS {quantity: 1, unit_price: 29.99, subtotal: 29.99}]->(p2); -- Query customer's order details MATCH (customer:Customer {id: 'cust_001'})-[:PLACED]->(order:Order)-[item:CONTAINS]->(product:Product) RETURN order.id, order.date, product.name, item.quantity, item.subtotal; </code></pre></div> <h4 id="pattern-6-metadata-nodes" class="position-relative d-flex align-items-center group"> Pattern 6: Metadata Nodes <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="pattern-6-metadata-nodes" aria-haspopup="dialog" aria-label="Share link: Pattern 6: Metadata Nodes"> Share link </button> </h4>Example: Tagging system <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Create content CREATE (post1:Post {id: 'post_001', title: 'Graph Modeling', content: '...'}); CREATE (post2:Post {id: 'post_002', title: 'GQL Syntax', content: '...'}); -- Create tags as nodes (not properties) CREATE (db_tag:Tag {name: 'databases'}); CREATE (graph_tag:Tag {name: 'graphs'}); CREATE (gql_tag:Tag {name: 'gql'}); -- Tag posts MATCH (post1:Post {id: 'post_001'}), (graph:Tag {name: 'graphs'}) CREATE (post1)-[:TAGGED_WITH]->(graph); MATCH (post1:Post {id: 'post_001'}), (db:Tag {name: 'databases'}) CREATE (post1)-[:TAGGED_WITH]->(db); MATCH (post2:Post {id: 'post_002'}), (gql:Tag {name: 'gql'}) CREATE (post2)-[:TAGGED_WITH]->(gql); -- Find all posts with a tag MATCH (post:Post)-[:TAGGED_WITH]->(tag:Tag {name: 'graphs'}) RETURN post.title; -- Find related posts (shared tags) MATCH (post:Post {id: 'post_001'})-[:TAGGED_WITH]->(tag:Tag)<-[:TAGGED_WITH]-(related:Post) WHERE post.id <> related.id RETURN related.title, count(tag) as shared_tags ORDER BY shared_tags DESC; </code></pre></div> <h3 id="modeling-anti-patterns-to-avoid" class="position-relative d-flex align-items-center group"> Modeling Anti-Patterns to Avoid <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-anti-patterns-to-avoid" aria-haspopup="dialog" aria-label="Share link: Modeling Anti-Patterns to Avoid"> Share link </button> </h3> <h4 id="anti-pattern-1-properties-as-nodes" class="position-relative d-flex align-items-center group"> Anti-Pattern 1: Properties as Nodes <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="anti-pattern-1-properties-as-nodes" aria-haspopup="dialog" aria-label="Share link: Anti-Pattern 1: Properties as Nodes"> Share link </button> </h4>Bad: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Don't create nodes for simple properties CREATE (alice:Person {id: 'person_001', name: 'Alice'}); CREATE (email:Email {value: 'alice@example.com'}); CREATE (age:Age {value: 30}); CREATE (alice)-[:HAS_EMAIL]->(email); CREATE (alice)-[:HAS_AGE]->(age); </code></pre></div>Good: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Store properties directly on the node CREATE (alice:Person { id: 'person_001', name: 'Alice', email: 'alice@example.com', age: 30 }); </code></pre></div>Exception: Create nodes for properties when: <ul> <li>Multiple entities share the same property value (e.g., addresses, phone numbers)</li> <li>You need to query or aggregate by that property independently</li> <li>The property has its own properties or relationships</li> </ul> <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Good: Shared address as node CREATE (home:Address { street: '123 Main St', city: 'New York', zip: '10001', country: 'USA' }); CREATE (alice:Person {name: 'Alice'})-[:LIVES_AT]->(home); CREATE (bob:Person {name: 'Bob'})-[:LIVES_AT]->(home); -- Now can query: Who lives at this address? MATCH (person:Person)-[:LIVES_AT]->(addr:Address {street: '123 Main St'}) RETURN person.name; </code></pre></div> <h4 id="anti-pattern-2-dense-nodes" class="position-relative d-flex align-items-center group"> Anti-Pattern 2: Dense Nodes <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="anti-pattern-2-dense-nodes" aria-haspopup="dialog" aria-label="Share link: Anti-Pattern 2: Dense Nodes"> Share link </button> </h4>Bad: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Avoid single nodes with millions of relationships CREATE (popular:User {name: 'Celebrity', followers: 10000000}); -- 10 million relationships // ... millions of (follower)-[:FOLLOWS]->(popular) ... -- Queries become slow MATCH (user:User {name: 'Celebrity'})<-[:FOLLOWS]-(follower) RETURN count(follower); -- Very slow! </code></pre></div>Good: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Use property for high-cardinality counts CREATE (popular:User {name: 'Celebrity', follower_count: 10000000}); -- Or use intermediate aggregation nodes CREATE (popular:User {name: 'Celebrity'}); CREATE (followers_2024_03:FollowerGroup { month: '2024-03', count: 50000 }); CREATE (popular)-[:HAS_FOLLOWER_GROUP]->(followers_2024_03); -- Individual followers connect to groups CREATE (follower)-[:MEMBER_OF]->(followers_2024_03); </code></pre></div> <h4 id="anti-pattern-3-relationship-types-as-properties" class="position-relative d-flex align-items-center group"> Anti-Pattern 3: Relationship Types as 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="anti-pattern-3-relationship-types-as-properties" aria-haspopup="dialog" aria-label="Share link: Anti-Pattern 3: Relationship Types as Properties"> Share link </button> </h4>Bad: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Don't use generic relationship type with type property CREATE (alice)-[:RELATED_TO {type: 'friend'}]->(bob); CREATE (alice)-[:RELATED_TO {type: 'coworker'}]->(carol); CREATE (alice)-[:RELATED_TO {type: 'family'}]->(dave); -- Can't efficiently query by relationship type MATCH (alice:Person {name: 'Alice'})-[r:RELATED_TO]->(other) WHERE r.type = 'friend' -- Must scan all relationships RETURN other.name; </code></pre></div>Good: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Use specific relationship types CREATE (alice)-[:FRIEND]->(bob); CREATE (alice)-[:COWORKER]->(carol); CREATE (alice)-[:FAMILY]->(dave); -- Efficient query by relationship type MATCH (alice:Person {name: 'Alice'})-[:FRIEND]->(friend) RETURN friend.name; </code></pre></div> <h4 id="anti-pattern-4-disconnected-nodes" class="position-relative d-flex align-items-center group"> Anti-Pattern 4: Disconnected Nodes <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="anti-pattern-4-disconnected-nodes" aria-haspopup="dialog" aria-label="Share link: Anti-Pattern 4: Disconnected Nodes"> Share link </button> </h4>Bad: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Avoid nodes with no relationships (unless temporary) CREATE (orphan:Product {id: 'prod_999', name: 'Orphan Product'}); -- No relationships to customers, orders, categories, etc. -- Hard to discover in queries MATCH (p:Product) WHERE NOT (p)--() RETURN p; -- Anti-pattern query </code></pre></div>Good: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Always connect nodes meaningfully CREATE (product:Product {id: 'prod_999', name: 'New Product'}); CREATE (category:Category {name: 'Electronics'}); CREATE (vendor:Vendor {name: 'Acme Corp'}); CREATE (product)-[:IN_CATEGORY]->(category); CREATE (vendor)-[:SUPPLIES]->(product); </code></pre></div> <h3 id="query-driven-modeling" class="position-relative d-flex align-items-center group"> Query-Driven 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="query-driven-modeling" aria-haspopup="dialog" aria-label="Share link: Query-Driven Modeling"> Share link </button> </h3> <h4 id="model-for-your-queries" class="position-relative d-flex align-items-center group"> Model for Your Queries <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="model-for-your-queries" aria-haspopup="dialog" aria-label="Share link: Model for Your Queries"> Share link </button> </h4>Design your graph to make common queries efficient: Example: Social network “news feed” query Requirement: Show posts from friends, ordered by time, with like counts. Model: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Users CREATE (alice:User {id: 'user_001', name: 'Alice'}); CREATE (bob:User {id: 'user_002', name: 'Bob'}); -- Friendship CREATE (alice)-[:FRIENDS_WITH]->(bob); -- Posts CREATE (post:Post { id: 'post_001', content: 'Loving graph databases!', timestamp: datetime('2024-03-15T10:30:00'), like_count: 0 -- Denormalize for performance }); CREATE (bob)-[:POSTED]->(post); -- Likes (still track individually for other queries) CREATE (alice)-[:LIKED {timestamp: datetime('2024-03-15T10:35:00')}]->(post); -- Increment like count MATCH (p:Post {id: 'post_001'}) SET p.like_count = p.like_count + 1; -- Efficient news feed query MATCH (me:User {id: 'user_001'})-[:FRIENDS_WITH]->(friend)-[:POSTED]->(post:Post) RETURN friend.name, post.content, post.timestamp, post.like_count ORDER BY post.timestamp DESC LIMIT 20; </code></pre></div> <h4 id="optimize-for-write-vs-read" class="position-relative d-flex align-items-center group"> Optimize for Write vs. Read <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="optimize-for-write-vs-read" aria-haspopup="dialog" aria-label="Share link: Optimize for Write vs. Read"> Share link </button> </h4>Write-optimized (normalized): <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Separate like tracking CREATE (user)-[:LIKED]->(post); -- Query count dynamically MATCH (post:Post {id: 'post_001'})<-[:LIKED]-(user) RETURN count(user) as like_count; </code></pre></div>Read-optimized (denormalized): <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Store count as property CREATE (post:Post {id: 'post_001', like_count: 0}); -- Update count on each like MATCH (post:Post {id: 'post_001'}) SET post.like_count = post.like_count + 1; -- Fast read MATCH (post:Post {id: 'post_001'}) RETURN post.like_count; </code></pre></div>Hybrid approach: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Both individual relationships AND denormalized count CREATE (user)-[:LIKED]->(post); MATCH (post:Post {id: 'post_001'}) SET post.like_count = post.like_count + 1; -- Fast reads from property, audit trail from relationships </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-new-node-types" class="position-relative d-flex align-items-center group"> Adding New Node Types <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-new-node-types" aria-haspopup="dialog" aria-label="Share link: Adding New Node Types"> Share link </button> </h4><div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Phase 1: Basic social network CREATE (alice:User {name: 'Alice'}); CREATE (bob:User {name: 'Bob'}); CREATE (alice)-[:FRIENDS_WITH]->(bob); -- Phase 2: Add posts (no migration needed!) CREATE (post:Post {content: 'Hello', author_id: 'alice'}); CREATE (alice)-[:POSTED]->(post); -- Phase 3: Add groups CREATE (group:Group {name: 'Graph DB Enthusiasts'}); CREATE (alice)-[:MEMBER_OF]->(group); CREATE (bob)-[:MEMBER_OF]->(group); -- Existing data unaffected </code></pre></div> <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><div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Add properties to existing nodes MATCH (alice:User {name: 'Alice'}) SET alice.email = 'alice@example.com', alice.joined_date = date('2024-01-15'); -- Add properties to new nodes only CREATE (carol:User { name: 'Carol', email: 'carol@example.com', joined_date: date('2024-03-20'), verification_status: 'verified' -- New property }); -- Query handles optional properties gracefully MATCH (user:User) RETURN user.name, user.email, user.verification_status; -- null for users without verification_status </code></pre></div> <h4 id="refactoring-relationships" class="position-relative d-flex align-items-center group"> Refactoring 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="refactoring-relationships" aria-haspopup="dialog" aria-label="Share link: Refactoring Relationships"> Share link </button> </h4><div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Old model: Generic "RELATED_TO" with type property MATCH (a:Person)-[r:RELATED_TO]->(b:Person) WHERE r.type = 'friend' -- Refactor to specific types MATCH (a:Person)-[old:RELATED_TO]->(b:Person) WHERE old.type = 'friend' CREATE (a)-[:FRIEND {since: old.since}]->(b) DELETE old; -- Now use specific relationship types MATCH (a:Person)-[:FRIEND]->(b:Person) RETURN b.name; </code></pre></div> <h3 id="performance-considerations" class="position-relative d-flex align-items-center group"> Performance Considerations <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-considerations" aria-haspopup="dialog" aria-label="Share link: Performance Considerations"> Share link </button> </h3> <h4 id="indexing-strategy" class="position-relative d-flex align-items-center group"> Indexing 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="indexing-strategy" aria-haspopup="dialog" aria-label="Share link: Indexing Strategy"> Share link </button> </h4><div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Create indexes on frequently queried properties CREATE INDEX user_email ON :User(email); CREATE INDEX product_sku ON :Product(sku); CREATE INDEX post_timestamp ON :Post(timestamp); -- Unique constraints (also create indexes) CREATE CONSTRAINT unique_user_id ON :User(id); CREATE CONSTRAINT unique_email ON :User(email); -- Composite indexes for multi-property queries CREATE INDEX user_city_age ON :User(city, age); -- Verify index usage with EXPLAIN EXPLAIN MATCH (u:User {email: 'alice@example.com'}) RETURN u; </code></pre></div> <h4 id="relationship-direction" class="position-relative d-flex align-items-center group"> Relationship Direction <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-direction" aria-haspopup="dialog" aria-label="Share link: Relationship Direction"> Share link </button> </h4><div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Model relationships in the direction of primary traversal -- Bad: Querying against relationship direction CREATE (product)-[:PURCHASED_BY]->(customer); MATCH (customer:Customer {id: 'cust_001'})<-[:PURCHASED_BY]-(product) -- Inefficient RETURN product; -- Good: Query with relationship direction CREATE (customer)-[:PURCHASED]->(product); MATCH (customer:Customer {id: 'cust_001'})-[:PURCHASED]->(product) RETURN product; </code></pre></div> <h4 id="limiting-relationship-counts" class="position-relative d-flex align-items-center group"> Limiting Relationship Counts <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="limiting-relationship-counts" aria-haspopup="dialog" aria-label="Share link: Limiting Relationship Counts"> Share link </button> </h4><div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Avoid nodes with unbounded relationship growth -- Use time-based partitioning or aggregation -- Time-partitioned events CREATE (user)-[:LOGGED_IN_2024_03]->(session); CREATE (user)-[:LOGGED_IN_2024_04]->(session); -- Periodic aggregation CREATE (user)-[:MONTHLY_ACTIVITY { month: '2024-03', login_count: 42, avg_session_duration: 1800 }]->(stats:ActivityStats); </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>Query Language: Optimizing GQL queries for your data model</li> <li>Performance: Indexing strategies and query optimization</li> <li>Best Practices: Production-ready modeling techniques</li> <li>Examples: Real-world modeling scenarios</li> <li>Architecture: Understanding Geode’s storage and indexing</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>Property Graph Model: Theoretical foundations</li> <li>Domain-Driven Design: Aligning models with business domains</li> <li>Normalization vs Denormalization: Trade-offs in graph modeling</li> <li>Graph Algorithms: Modeling for algorithmic analysis</li> <li>Migration Strategies: Evolving schemas in production</li> </ul> <hr> Effective graph modeling transforms complex domains into intuitive, performant graph structures. By understanding core patterns, avoiding anti-patterns, and optimizing for your query patterns, you can build graph models that scale with your application and delight your users with fast, expressive queries.

Popular

Related Articles

Graph Schema Design Guide