Graph Schema Design Guide | Geode Database

<h3 id="overview" class="position-relative d-flex align-items-center group"> Overview <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="overview" aria-haspopup="dialog" aria-label="Share link: Overview"> 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>Designing an effective graph schema is critical for query performance, maintainability, and accurately representing your domain. This guide covers best practices for modeling data as property graphs in Geode. Key Principles: <ol> <li>Model the domain, not the data - Think in relationships, not tables</li> <li>Optimize for queries, not storage - Denormalization is often beneficial</li> <li>Use labels for types, properties for attributes - Clear separation of concerns</li> <li>Make relationships meaningful - Every edge should represent a real connection</li> </ol> Quick Links: <ul> <li><a href="https://geodedb.com/docs/guides/schema-design/#property-graph-fundamentals" >Property Graph Fundamentals</a> </li> <li><a href="https://geodedb.com/docs/guides/schema-design/#node-label-design" >Node Label Design</a> </li> <li><a href="https://geodedb.com/docs/guides/schema-design/#relationship-type-design" >Relationship Type Design</a> </li> <li><a href="https://geodedb.com/docs/guides/schema-design/#property-design-patterns" >Property Design Patterns</a> </li> <li><a href="https://geodedb.com/docs/guides/schema-design/#domain-examples" >Domain Examples</a> </li> <li><a href="https://geodedb.com/docs/guides/schema-design/#common-antipatterns" >Common Antipatterns</a> </li> </ul> <hr> <h3 id="property-graph-fundamentals" class="position-relative d-flex align-items-center group"> Property Graph Fundamentals <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-fundamentals" aria-haspopup="dialog" aria-label="Share link: Property Graph Fundamentals"> Share link </button> </h3> <h4 id="core-concepts" class="position-relative d-flex align-items-center group"> Core 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-concepts" aria-haspopup="dialog" aria-label="Share link: Core Concepts"> Share link </button> </h4>A property graph consists of: <ol> <li> Nodes (vertices) - Entities in your domain <ul> <li>Have one or more labels (types/categories)</li> <li>Contain properties (key-value pairs)</li> <li>Uniquely identified by internal ID</li> </ul> </li> <li> Relationships (edges) - Connections between nodes <ul> <li>Have exactly one type (name)</li> <li>Are directed (have start and end nodes)</li> <li>Contain properties (key-value pairs)</li> <li>Uniquely identified by internal ID</li> </ul> </li> <li> Properties - Key-value attributes <ul> <li>Keys are strings</li> <li>Values can be 50+ data types (strings, numbers, dates, vectors, etc.)</li> <li>Stored on nodes or relationships</li> </ul> </li> </ol> <h4 id="example-graph" class="position-relative d-flex align-items-center group"> Example Graph <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="example-graph" aria-haspopup="dialog" aria-label="Share link: Example Graph"> Share link </button> </h4><div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Nodes with labels and properties (alice:Person {name: "Alice", age: 30, email: "[email protected]"}) (bob:Person {name: "Bob", age: 25}) (acme:Company {name: "Acme Corp", founded: 2010}) -- Relationships with types and properties (alice)-[:KNOWS {since: 2020, closeness: 0.8}]->(bob) (alice)-[:WORKS_AT {role: "Engineer", since: 2022}]->(acme) </code></pre></div><hr> <h3 id="node-label-design" class="position-relative d-flex align-items-center group"> Node Label Design <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-label-design" aria-haspopup="dialog" aria-label="Share link: Node Label Design"> Share link </button> </h3> <h4 id="labeling-strategy" class="position-relative d-flex align-items-center group"> Labeling 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="labeling-strategy" aria-haspopup="dialog" aria-label="Share link: Labeling Strategy"> Share link </button> </h4>Labels represent entity types - Use them to categorize nodes. <h5 id="-good-labeling-patterns" class="position-relative d-flex align-items-center group"> ✅ Good Labeling 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="-good-labeling-patterns" aria-haspopup="dialog" aria-label="Share link: ✅ Good Labeling Patterns"> Share link </button> </h5>1. Use Clear, Singular Nouns <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- GOOD Person, Company, Product, Order, Review -- BAD People, Companies, person_table, usr </code></pre></div>2. Use Multi-Label for Subtypes <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- GOOD: Person with specific roles (alice:Person:Employee {name: "Alice"}) (bob:Person:Customer {name: "Bob"}) (charlie:Person:Employee:Manager {name: "Charlie"}) -- Query specific subtypes MATCH (e:Employee) RETURN e -- All employees MATCH (m:Manager) RETURN m -- All managers MATCH (p:Person:!Employee) RETURN p -- People who aren't employees </code></pre></div>3. Use Meaningful Hierarchies <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- GOOD: Product categories (laptop:Product:Electronics:Computer {brand: "Dell"}) (shirt:Product:Clothing:Apparel {size: "M"}) -- Query at different levels MATCH (e:Electronics) RETURN e -- All electronics MATCH (c:Computer) RETURN c -- Just computers </code></pre></div> <h5 id="-bad-labeling-antipatterns" class="position-relative d-flex align-items-center group"> ❌ Bad Labeling Antipatterns <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="-bad-labeling-antipatterns" aria-haspopup="dialog" aria-label="Share link: ❌ Bad Labeling Antipatterns"> Share link </button> </h5>1. Encoding Values in Labels (Dynamic Labels) <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- BAD: Don't create labels from data (alice:Person:Age30:Female {name: "Alice"}) -- GOOD: Use properties (alice:Person {name: "Alice", age: 30, gender: "female"}) </code></pre></div>2. Too Many Labels <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- BAD: Label explosion (alice:Person:Employee:Engineer:Senior:FullStack:JavaScript:Remote) -- GOOD: Use selective labels + properties (alice:Person:Employee { name: "Alice", level: "Senior", role: "Engineer", stack: "FullStack", skills: ["JavaScript", "Python"], location: "Remote" }) </code></pre></div>3. Generic Labels <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- BAD: Too generic, hard to query (thing1:Entity {type: "person", name: "Alice"}) (thing2:Entity {type: "company", name: "Acme"}) -- GOOD: Specific labels (alice:Person {name: "Alice"}) (acme:Company {name: "Acme"}) </code></pre></div> <h4 id="label-naming-conventions" class="position-relative d-flex align-items-center group"> Label Naming Conventions <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="label-naming-conventions" aria-haspopup="dialog" aria-label="Share link: Label Naming Conventions"> Share link </button> </h4><table> <thead> <tr> <th>Convention</th> <th>Example</th> <th>Use Case</th> </tr> </thead> <tbody> <tr> <td>PascalCase</td> <td><code>Person</code>, <code>OrderItem</code></td> <td>Recommended - clear, standard</td> </tr> <tr> <td>UPPER_SNAKE</td> <td><code>PURCHASE_ORDER</code></td> <td>Legacy systems integration</td> </tr> <tr> <td>Namespacing</td> <td><code>app:User</code>, <code>sys:Config</code></td> <td>Multi-tenant or modular systems</td> </tr> </tbody> </table> Recommendation: Use PascalCase for consistency with GQL standards. <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Recommended naming CREATE (p:Person {name: "Alice"}) CREATE (o:PurchaseOrder {id: 12345}) CREATE (li:LineItem {quantity: 5}) </code></pre></div><hr> <h3 id="relationship-type-design" class="position-relative d-flex align-items-center group"> Relationship Type Design <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-type-design" aria-haspopup="dialog" aria-label="Share link: Relationship Type Design"> Share link </button> </h3> <h4 id="relationship-naming" class="position-relative d-flex align-items-center group"> Relationship Naming <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-naming" aria-haspopup="dialog" aria-label="Share link: Relationship Naming"> Share link </button> </h4>Relationship types describe the connection - Use verbs or verb phrases. <h5 id="-good-relationship-patterns" class="position-relative d-flex align-items-center group"> ✅ Good Relationship 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="-good-relationship-patterns" aria-haspopup="dialog" aria-label="Share link: ✅ Good Relationship Patterns"> Share link </button> </h5>1. Use Active Verbs (Past or Present Tense) <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- GOOD: Clear, descriptive (alice:Person)-[:KNOWS]->(bob:Person) (alice:Person)-[:WORKS_AT]->(acme:Company) (order:Order)-[:CONTAINS]->(item:Product) (user:User)-[:PURCHASED]->(product:Product) (employee:Employee)-[:REPORTS_TO]->(manager:Employee) </code></pre></div>2. Direction Matters <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- GOOD: Relationship direction is meaningful (parent:Person)-[:PARENT_OF]->(child:Person) -- Query respects direction MATCH (p:Person)-[:PARENT_OF]->(c:Person) RETURN p.name AS parent, c.name AS child -- Reverse direction MATCH (c:Person)<-[:PARENT_OF]-(p:Person) RETURN p.name AS parent, c.name AS child </code></pre></div>3. Use Specific Types <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- GOOD: Specific relationship types (alice:Person)-[:MANAGES]->(team:Team) (alice:Person)-[:WORKS_ON]->(project:Project) (alice:Person)-[:MENTORS]->(bob:Person) -- BAD: Generic types (alice:Person)-[:RELATED_TO {type: "manages"}]->(team:Team) </code></pre></div> <h5 id="-bad-relationship-antipatterns" class="position-relative d-flex align-items-center group"> ❌ Bad Relationship Antipatterns <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="-bad-relationship-antipatterns" aria-haspopup="dialog" aria-label="Share link: ❌ Bad Relationship Antipatterns"> Share link </button> </h5>1. Encoding Values in Type Names <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- BAD: Dynamic relationship types (alice)-[:KNOWS_SINCE_2020]->(bob) (alice)-[:FRIEND_CLOSENESS_0.8]->(charlie) -- GOOD: Use properties (alice)-[:KNOWS {since: 2020}]->(bob) (alice)-[:FRIEND {closeness: 0.8}]->(charlie) </code></pre></div>2. Bidirectional Relationships <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- BAD: Creating duplicate relationships (alice)-[:KNOWS]->(bob) (bob)-[:KNOWS]->(alice) -- GOOD: Use single direction + queries (alice)-[:KNOWS]->(bob) -- Query both directions MATCH (a:Person)-[:KNOWS]-(b:Person) -- Ignores direction WHERE a.name = "Alice" RETURN b.name </code></pre></div>3. Missing Relationship Types <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- BAD: Properties on nodes instead of relationships (alice:Person {friendsWith: ["Bob", "Charlie"]}) -- GOOD: Explicit relationships (alice:Person)-[:KNOWS]->(bob:Person) (alice:Person)-[:KNOWS]->(charlie:Person) </code></pre></div> <h4 id="relationship-properties" class="position-relative d-flex align-items-center group"> Relationship 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="relationship-properties" aria-haspopup="dialog" aria-label="Share link: Relationship Properties"> Share link </button> </h4>Properties on relationships capture connection metadata. <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Social network relationships (alice)-[:KNOWS { since: date('2020-01-15'), strength: 0.8, context: "university", interactions: 147 }]->(bob) -- Employment relationships (alice)-[:WORKS_AT { role: "Senior Engineer", department: "Engineering", startDate: date('2022-03-01'), salary: 150000, employmentType: "full-time" }]->(acme) -- Transaction relationships (order)-[:CONTAINS { quantity: 3, unitPrice: 29.99, discount: 0.1, addedAt: timestamp() }]->(product) </code></pre></div><hr> <h3 id="property-design-patterns" class="position-relative d-flex align-items-center group"> Property 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="property-design-patterns" aria-haspopup="dialog" aria-label="Share link: Property Design Patterns"> Share link </button> </h3> <h4 id="property-selection" class="position-relative d-flex align-items-center group"> Property Selection <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-selection" aria-haspopup="dialog" aria-label="Share link: Property Selection"> Share link </button> </h4>Properties store attributes of nodes and relationships. <h5 id="-when-to-use-properties" class="position-relative d-flex align-items-center group"> ✅ When to Use 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="-when-to-use-properties" aria-haspopup="dialog" aria-label="Share link: ✅ When to Use Properties"> Share link </button> </h5><ol> <li>Attributes of the entity itself</li> </ol> <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">(person:Person { name: "Alice", age: 30, email: "[email protected]", bio: "Software engineer..." }) </code></pre></div><ol start="2"> <li>Frequently filtered/sorted values</li> </ol> <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Create indexes for these (product:Product { price: 29.99, -- Frequently filtered category: "Books", -- Frequently filtered rating: 4.5, -- Frequently sorted stock: 100 }) -- Efficient queries CREATE INDEX product_price ON Product(price); MATCH (p:Product) WHERE p.price < 50 RETURN p; </code></pre></div><ol start="3"> <li>Temporal data</li> </ol> <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">(event:Event { title: "Launch Party", startTime: timestamp('2026-03-15T19:00:00Z'), endTime: timestamp('2026-03-15T23:00:00Z'), timezone: 'America/New_York' }) </code></pre></div> <h5 id="-when-not-to-use-properties" class="position-relative d-flex align-items-center group"> ❌ When NOT to Use 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="-when-not-to-use-properties" aria-haspopup="dialog" aria-label="Share link: ❌ When NOT to Use Properties"> Share link </button> </h5>1. Relationships Disguised as Properties <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- BAD: Lists of related IDs (person:Person { name: "Alice", friendIds: [10, 20, 30, 40] -- Don't do this }) -- GOOD: Explicit relationships (alice:Person)-[:KNOWS]->(bob:Person) (alice:Person)-[:KNOWS]->(charlie:Person) </code></pre></div>2. Computed/Aggregated Data (Usually) <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- BAD: Redundant computed values (person:Person { name: "Alice", friendCount: 15, -- This can be queried avgFriendAge: 28.5 -- This can be computed }) -- GOOD: Compute on demand MATCH (p:Person {name: "Alice"})-[:KNOWS]->(friend) RETURN p.name, count(friend) AS friendCount, avg(friend.age) AS avgFriendAge -- EXCEPTION: Precompute for performance (materialized views/caching) -- If counting friends is very slow, denormalize (person:Person {name: "Alice", cachedFriendCount: 15}) -- But update on every friend add/remove </code></pre></div> <h4 id="property-types" class="position-relative d-flex align-items-center group"> Property 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="property-types" aria-haspopup="dialog" aria-label="Share link: Property Types"> Share link </button> </h4>Geode supports 50+ data types. Choose appropriate types: <table> <thead> <tr> <th>Data Type</th> <th>Use Case</th> <th>Example</th> </tr> </thead> <tbody> <tr> <td><code>String</code>, <code>Text</code></td> <td>Names, descriptions</td> <td><code>name: "Alice"</code></td> </tr> <tr> <td><code>Int</code>, <code>BigInt</code></td> <td>IDs, counts</td> <td><code>id: 12345, age: 30</code></td> </tr> <tr> <td><code>Real</code>, <code>Double</code></td> <td>Prices, ratings</td> <td><code>price: 29.99, rating: 4.5</code></td> </tr> <tr> <td><code>Date</code>, <code>Timestamp</code></td> <td>Temporal data</td> <td><code>created: date('2026-01-23')</code></td> </tr> <tr> <td><code>Boolean</code></td> <td>Flags</td> <td><code>active: true, verified: false</code></td> </tr> <tr> <td><code>VectorF32</code></td> <td>ML embeddings</td> <td><code>embedding: vectorf32([0.1, 0.2, ...])</code></td> </tr> <tr> <td><code>Json</code>, <code>Jsonb</code></td> <td>Semi-structured data</td> <td><code>metadata: jsonb('{"key": "value"}')</code></td> </tr> <tr> <td><code>List</code></td> <td>Multiple values</td> <td><code>tags: ["tech", "database"]</code></td> </tr> <tr> <td><code>GeoPoint</code></td> <td>Geographic locations</td> <td><code>location: geopoint(37.7749, -122.4194)</code></td> </tr> </tbody> </table> Type Selection Tips: <ul> <li>Use specific types for better validation and performance</li> <li>Avoid generic <code>Text</code> when <code>Varchar(255)</code> suffices</li> <li>Use <code>Jsonb</code> for flexible schemas (but index key properties separately)</li> <li>Use vectors for similarity search (embeddings, recommendations)</li> </ul> <hr> <h3 id="domain-examples" class="position-relative d-flex align-items-center group"> Domain Examples <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-examples" aria-haspopup="dialog" aria-label="Share link: Domain Examples"> Share link </button> </h3> <h4 id="example-1-social-network" class="position-relative d-flex align-items-center group"> Example 1: Social Network <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="example-1-social-network" aria-haspopup="dialog" aria-label="Share link: Example 1: Social Network"> Share link </button> </h4>Entities: People, Posts, Comments, Likes Relationships: KNOWS, POSTED, COMMENTED_ON, LIKED <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Schema design (alice:Person { id: 1, name: "Alice", email: "[email protected]", joinedAt: timestamp(), bio: "Software engineer" }) (post:Post { id: 101, title: "Graph Databases", content: "Graph databases are...", createdAt: timestamp(), tags: ["tech", "databases"] }) (comment:Comment { id: 501, content: "Great post!", createdAt: timestamp() }) -- Relationships (alice)-[:KNOWS {since: date('2020-01-01'), closeness: 0.8}]->(bob) (alice)-[:POSTED {createdAt: timestamp()}]->(post) (bob)-[:COMMENTED_ON {createdAt: timestamp()}]->(post) (bob)-[:WROTE]->(comment) (comment)-[:ON]->(post) (alice)-[:LIKED {likedAt: timestamp()}]->(post) </code></pre></div>Key Queries: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Find Alice's friends MATCH (alice:Person {name: "Alice"})-[:KNOWS]->(friend:Person) RETURN friend.name -- Find posts by Alice's friends MATCH (alice:Person {name: "Alice"})-[:KNOWS]->(friend)-[:POSTED]->(post:Post) RETURN post.title, friend.name ORDER BY post.createdAt DESC -- Find popular posts (most likes) MATCH (p:Post)<-[:LIKED]-(u:User) RETURN p.title, count(u) AS likes ORDER BY likes DESC LIMIT 10 </code></pre></div> <h4 id="example-2-e-commerce" class="position-relative d-flex align-items-center group"> Example 2: 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="example-2-e-commerce" aria-haspopup="dialog" aria-label="Share link: Example 2: E-Commerce"> Share link </button> </h4>Entities: Customer, Product, Order, LineItem, Category Relationships: PURCHASED, CONTAINS, IN_CATEGORY, REVIEWED <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Schema design (customer:Customer { id: 1, name: "Alice", email: "[email protected]", memberSince: date('2020-01-01') }) (product:Product { id: 101, name: "Laptop", price: 999.99, stock: 50, sku: "LAP-001" }) (category:Category { id: 10, name: "Electronics", slug: "electronics" }) (order:Order { id: 5001, orderDate: timestamp(), status: "shipped", total: 1049.98 }) (lineItem:LineItem { quantity: 1, unitPrice: 999.99, subtotal: 999.99 }) -- Relationships (customer)-[:PURCHASED {date: timestamp()}]->(order) (order)-[:CONTAINS]->(lineItem) (lineItem)-[:OF_PRODUCT]->(product) (product)-[:IN_CATEGORY]->(category) (customer)-[:REVIEWED {rating: 5, date: timestamp()}]->(product) </code></pre></div>Key Queries: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Find customer's order history MATCH (c:Customer {email: "[email protected]"})-[:PURCHASED]->(o:Order) -[:CONTAINS]->(li:LineItem)-[:OF_PRODUCT]->(p:Product) RETURN o.orderDate, o.total, collect(p.name) AS products ORDER BY o.orderDate DESC -- Product recommendations (customers who bought this also bought...) MATCH (p1:Product {id: 101})<-[:OF_PRODUCT]-(:LineItem) <-[:CONTAINS]-(o:Order)<-[:PURCHASED]-(c:Customer) -[:PURCHASED]->(o2:Order)-[:CONTAINS]->(:LineItem) -[:OF_PRODUCT]->(p2:Product) WHERE p1 <> p2 RETURN p2.name, count(*) AS frequency ORDER BY frequency DESC LIMIT 5 </code></pre></div> <h4 id="example-3-knowledge-graph" class="position-relative d-flex align-items-center group"> Example 3: Knowledge Graph <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="example-3-knowledge-graph" aria-haspopup="dialog" aria-label="Share link: Example 3: Knowledge Graph"> Share link </button> </h4>Entities: Concept, Document, Author, Citation Relationships: RELATED_TO, AUTHORED, CITES, HAS_TOPIC <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Schema design (concept:Concept { id: 1, name: "Graph Databases", definition: "A database that uses graph structures...", embedding: vectorf32([0.1, 0.2, 0.3, ...]) -- For similarity search }) (doc:Document { id: 101, title: "Introduction to Graph Theory", abstract: "This paper introduces...", publishedDate: date('2025-06-15'), embedding: vectorf32([...]) -- For semantic search }) (author:Author { id: 201, name: "Dr. Alice Smith", institution: "MIT", hIndex: 45 }) -- Relationships (concept1:Concept)-[:RELATED_TO {strength: 0.8}]->(concept2:Concept) (author)-[:AUTHORED {role: "primary"}]->(doc) (doc)-[:HAS_TOPIC]->(concept) (doc1)-[:CITES {context: "methodology"}]->(doc2) </code></pre></div>Key Queries: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Find related concepts (via vector similarity) MATCH (c:Concept {name: "Graph Databases"}) MATCH (related:Concept) WHERE vector_cosine(c.embedding, related.embedding) > 0.7 AND c <> related RETURN related.name, vector_cosine(c.embedding, related.embedding) AS similarity ORDER BY similarity DESC LIMIT 10 -- Find influential papers (high citation count) MATCH (doc:Document)<-[:CITES]-(citing:Document) RETURN doc.title, count(citing) AS citations ORDER BY citations DESC LIMIT 20 -- Find collaboration networks MATCH (a1:Author)-[:AUTHORED]->(doc:Document)<-[:AUTHORED]-(a2:Author) WHERE a1 <> a2 RETURN a1.name, a2.name, count(doc) AS collaborations ORDER BY collaborations DESC </code></pre></div> <h4 id="example-4-fraud-detection" class="position-relative d-flex align-items-center group"> Example 4: Fraud Detection <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="example-4-fraud-detection" aria-haspopup="dialog" aria-label="Share link: Example 4: Fraud Detection"> Share link </button> </h4>Entities: Account, Transaction, Device, IP Address Relationships: OWNS, INITIATED, USED, FROM_IP <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Schema design (account:Account { id: 1, accountNumber: "1234567890", status: "active", riskScore: 0.3 }) (txn:Transaction { id: 5001, amount: 150.00, timestamp: timestamp(), status: "completed", flagged: false }) (device:Device { id: "device-abc123", type: "mobile", os: "iOS", fingerprint: "abcd1234..." }) (ip:IPAddress { address: "192.168.1.100", country: "US", riskLevel: "low" }) -- Relationships (account)-[:INITIATED {timestamp: timestamp()}]->(txn) (txn)-[:USED]->(device) (txn)-[:FROM_IP]->(ip) (account)-[:OWNS]->(device) </code></pre></div>Fraud Detection Queries: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Find accounts using same device (account takeover) MATCH (a1:Account)-[:OWNS]->(d:Device)<-[:OWNS]-(a2:Account) WHERE a1 <> a2 RETURN a1.accountNumber, a2.accountNumber, d.fingerprint -- Find transactions from high-risk IPs MATCH (txn:Transaction)-[:FROM_IP]->(ip:IPAddress) WHERE ip.riskLevel = "high" RETURN txn.id, txn.amount, ip.address, ip.country -- Detect unusual transaction patterns MATCH (account:Account)-[:INITIATED]->(txn:Transaction) WITH account, avg(txn.amount) AS avgAmount, stddev(txn.amount) AS stdDev MATCH (account)-[:INITIATED]->(recent:Transaction) WHERE recent.timestamp > timestamp() - duration('PT24H') AND abs(recent.amount - avgAmount) > 3 * stdDev RETURN account.accountNumber, recent.id, recent.amount, avgAmount, stdDev </code></pre></div><hr> <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-labelsproperties" class="position-relative d-flex align-items-center group"> Adding New Labels/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-new-labelsproperties" aria-haspopup="dialog" aria-label="Share link: Adding New Labels/Properties"> Share link </button> </h4><div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Add new label to existing nodes MATCH (e:Employee) WHERE e.role = "Manager" SET e:Manager -- Add new property with default MATCH (p:Product) WHERE p.stock IS NULL SET p.stock = 0 -- Add computed property MATCH (p:Person)-[k:KNOWS]->(friend) WITH p, count(friend) AS friendCount SET p.cachedFriendCount = friendCount </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><div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Split generic relationship into specific types MATCH (a:Account)-[r:RELATED_TO {type: "owns"}]->(b:Account) CREATE (a)-[:OWNS {since: r.createdAt}]->(b) DELETE r -- Merge duplicate relationships MATCH (a:Person)-[r:KNOWS]->(b:Person) WITH a, b, collect(r) AS rels WHERE size(rels) > 1 CREATE (a)-[:KNOWS {since: min([rel IN rels | rel.since])}]->(b) FOREACH (rel IN rels | DELETE rel) </code></pre></div> <h4 id="handling-breaking-changes" class="position-relative d-flex align-items-center group"> Handling Breaking Changes <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="handling-breaking-changes" aria-haspopup="dialog" aria-label="Share link: Handling Breaking Changes"> Share link </button> </h4><div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Create new property, migrate, then deprecate old -- Step 1: Add new property MATCH (p:Product) SET p.priceInCents = toInt(p.price * 100) -- Step 2: Update application to use priceInCents -- Step 3: Remove old property (after migration) MATCH (p:Product) REMOVE p.price </code></pre></div><hr> <h3 id="common-antipatterns" class="position-relative d-flex align-items-center group"> Common Antipatterns <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-antipatterns" aria-haspopup="dialog" aria-label="Share link: Common Antipatterns"> Share link </button> </h3> <h4 id="-antipattern-1-treating-graph-like-relational" class="position-relative d-flex align-items-center group"> ❌ Antipattern 1: Treating Graph Like Relational <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="-antipattern-1-treating-graph-like-relational" aria-haspopup="dialog" aria-label="Share link: ❌ Antipattern 1: Treating Graph Like Relational"> Share link </button> </h4>Bad: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Treating nodes as relational tables with foreign keys (order:Order {id: 1, customerId: 42, productId: 101}) </code></pre></div>Good: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Use explicit relationships (customer:Customer {id: 42})-[:PURCHASED]->(order:Order {id: 1}) (order)-[:CONTAINS]->(:LineItem)-[:OF_PRODUCT]->(product:Product {id: 101}) </code></pre></div> <h4 id="-antipattern-2-dense-nodes-supernodes" class="position-relative d-flex align-items-center group"> ❌ Antipattern 2: Dense Nodes (Supernodes) <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="-antipattern-2-dense-nodes-supernodes" aria-haspopup="dialog" aria-label="Share link: ❌ Antipattern 2: Dense Nodes (Supernodes)"> Share link </button> </h4>Problem: Nodes with millions of relationships cause performance issues. Bad: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Every user connected to same "System" node (user1:User)-[:REGISTERED_IN]->(system:System) (user2:User)-[:REGISTERED_IN]->(system:System) -- ... millions of users </code></pre></div>Good: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Partition by time/category (user1:User {registeredAt: timestamp()}) (user2:User {registeredAt: timestamp()}) -- Or use properties instead (user:User {systemId: "main", registeredAt: timestamp()}) </code></pre></div> <h4 id="-antipattern-3-over-indexing" class="position-relative d-flex align-items-center group"> ❌ Antipattern 3: Over-Indexing <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="-antipattern-3-over-indexing" aria-haspopup="dialog" aria-label="Share link: ❌ Antipattern 3: Over-Indexing"> Share link </button> </h4>Bad: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Creating indexes on every property CREATE INDEX person_name ON Person(name); CREATE INDEX person_age ON Person(age); CREATE INDEX person_email ON Person(email); CREATE INDEX person_city ON Person(city); CREATE INDEX person_zip ON Person(zip); CREATE INDEX person_created ON Person(createdAt); -- Too many indexes slow down writes </code></pre></div>Good: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Index only frequently queried/filtered properties CREATE INDEX person_email ON Person(email); -- Unique lookups CREATE INDEX person_name ON Person(name); -- Search by name -- Skip indexes on rarely queried properties </code></pre></div> <h4 id="-antipattern-4-ignoring-cardinality" class="position-relative d-flex align-items-center group"> ❌ Antipattern 4: Ignoring 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="-antipattern-4-ignoring-cardinality" aria-haspopup="dialog" aria-label="Share link: ❌ Antipattern 4: Ignoring Cardinality"> Share link </button> </h4>Problem: Not considering relationship cardinality. Bad: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Many-to-many without intermediate node (student:Student)-[:ENROLLED_IN {grade: "A"}]->(course:Course) -- What if student takes course multiple times? </code></pre></div>Good: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Use intermediate node for many-to-many (student:Student)-[:HAS]->(enrollment:Enrollment { grade: "A", semester: "Fall 2025", year: 2025 })-[:IN]->(course:Course) </code></pre></div><hr> <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>Index properties used in: <ol> <li>Exact matches: <code>WHERE p.email = '[email protected]'</code></li> <li>Range queries: <code>WHERE p.age > 30</code></li> <li>Sorting: <code>ORDER BY p.name</code></li> </ol> <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Create appropriate index types CREATE INDEX person_email ON Person(email); -- B-tree for exact/range CREATE FULLTEXT INDEX person_bio ON Person(bio); -- Full-text search CREATE VECTOR INDEX doc_embed ON Document(embedding); -- Vector similarity CREATE SPATIAL INDEX loc_coords ON Location(coords); -- Geo queries </code></pre></div> <h4 id="query-optimization" class="position-relative d-flex align-items-center group"> Query Optimization <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="query-optimization" aria-haspopup="dialog" aria-label="Share link: Query Optimization"> Share link </button> </h4>Principle: Start with specific, indexed lookups, then expand. <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- GOOD: Start with indexed lookup MATCH (alice:Person {email: "[email protected]"}) -- Index seek MATCH (alice)-[:KNOWS]->(friend) RETURN friend.name -- BAD: Full scan first MATCH (p:Person)-[:KNOWS]->(friend) WHERE p.email = "[email protected]" -- Scans all persons first RETURN friend.name </code></pre></div><hr> <h3 id="next-steps" class="position-relative d-flex align-items-center group"> Next Steps <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="next-steps" aria-haspopup="dialog" aria-label="Share link: Next Steps"> Share link </button> </h3><ul> <li><a href="/docs/model/data-model-and-types/" >Data Types Reference</a> - Complete type system</li> <li><a href="/docs/query/performance-tuning/" >Query Performance</a> - Optimize queries with EXPLAIN/PROFILE</li> <li><a href="/docs/query/indexing-and-optimization/" >Indexing Guide</a> - Index types and strategies</li> <li><a href="/docs/gql/guide/" >GQL Guide</a> - Query language syntax</li> <li><a href="/docs/guides/migration-guide/" >Migration Guide</a> - Migrate from other graph databases</li> </ul>