Category: Graph Databases 101

The Graph Databases 101 category provides foundational knowledge for understanding graph databases, their unique characteristics, and when to use them. Whether you’re new to graph databases or coming from relational databases, these resources help you build a solid conceptual foundation. <h3 id="introduction-to-graph-databases" class="position-relative d-flex align-items-center group"> Introduction to Graph Databases <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-databases" aria-haspopup="dialog" aria-label="Share link: Introduction to Graph Databases"> 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 databases represent and store data as networks of interconnected nodes and relationships. Unlike traditional relational databases that use tables and foreign keys, graph databases make relationships first-class citizens of the data model, enabling natural representation of connected data and efficient traversal queries. The graph database paradigm has gained prominence as applications increasingly need to model and query complex, interconnected data: social networks, recommendation engines, fraud detection systems, knowledge graphs, and network topology analysis all benefit from graph database technology. Geode implements the ISO/IEC 39075:2024 Graph Query Language (GQL) standard, providing a standardized, SQL-like approach to working with graph data. This makes graph databases more accessible to developers familiar with relational databases while preserving the power and flexibility of graph thinking. <h3 id="what-is-a-graph-database" class="position-relative d-flex align-items-center group"> What is a Graph Database? <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-a-graph-database" aria-haspopup="dialog" aria-label="Share link: What is a Graph Database?"> Share link </button> </h3> <h4 id="the-graph-data-model" class="position-relative d-flex align-items-center group"> The Graph Data 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="the-graph-data-model" aria-haspopup="dialog" aria-label="Share link: The Graph Data Model"> Share link </button> </h4>A graph consists of three fundamental elements: Nodes (also called vertices): <ul> <li>Represent entities in your domain (people, products, places, concepts)</li> <li>Can have one or more labels categorizing their type</li> <li>Store properties as key-value pairs</li> </ul> <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">(alice:Person { name: 'Alice Anderson', age: 30, email: 'alice@example.com' }) </code></pre></div>Relationships (also called edges): <ul> <li>Connect two nodes with a specific, meaningful connection</li> <li>Have a type that describes the nature of the connection</li> <li>Are directed (have a start node and end node)</li> <li>Can store properties describing the relationship</li> </ul> <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-[:KNOWS { since: 2020, relationship_type: 'colleague' }]-> </code></pre></div>Properties: <ul> <li>Key-value pairs attached to nodes or relationships</li> <li>Support various data types: strings, numbers, booleans, dates, lists, maps</li> <li>Enable rich descriptions of entities and connections</li> </ul> <h4 id="a-simple-example" class="position-relative d-flex align-items-center group"> A Simple 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="a-simple-example" aria-haspopup="dialog" aria-label="Share link: A Simple Example"> Share link </button> </h4>Representing a small social network: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Create people CREATE (alice:Person {name: 'Alice', city: 'New York'}); CREATE (bob:Person {name: 'Bob', city: 'San Francisco'}); CREATE (carol:Person {name: 'Carol', city: 'New York'}); -- Create relationships MATCH (a:Person {name: 'Alice'}), (b:Person {name: 'Bob'}) CREATE (a)-[:KNOWS {since: 2020}]->(b); MATCH (a:Person {name: 'Alice'}), (c:Person {name: 'Carol'}) CREATE (a)-[:KNOWS {since: 2019}]->(c); -- Query: Who does Alice know? MATCH (alice:Person {name: 'Alice'})-[:KNOWS]->(friend) RETURN friend.name, friend.city; </code></pre></div> <h3 id="why-use-a-graph-database" class="position-relative d-flex align-items-center group"> Why Use a Graph Database? <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="why-use-a-graph-database" aria-haspopup="dialog" aria-label="Share link: Why Use a Graph Database?"> Share link </button> </h3> <h4 id="relationship-centric-data" class="position-relative d-flex align-items-center group"> Relationship-Centric Data <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-centric-data" aria-haspopup="dialog" aria-label="Share link: Relationship-Centric Data"> Share link </button> </h4>Problem: Traditional databases struggle with deeply connected data. Relational approach (SQL): <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-sql" data-lang="sql">-- Multiple self-joins get expensive quickly SELECT DISTINCT p4.name FROM persons p1 JOIN friendships f1 ON p1.id = f1.person1_id JOIN persons p2 ON f1.person2_id = p2.id JOIN friendships f2 ON p2.id = f2.person1_id JOIN persons p3 ON f2.person2_id = p3.id JOIN friendships f3 ON p3.id = f3.person1_id JOIN persons p4 ON f3.person2_id = p4.id WHERE p1.name = 'Alice'; -- Friends of friends of friends: 3 joins </code></pre></div>Graph approach (GQL): <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Natural, efficient pattern matching MATCH (alice:Person {name: 'Alice'})-[:KNOWS*1..3]->(connection) RETURN DISTINCT connection.name; -- Friends up to 3 hops: simple and fast </code></pre></div> <h4 id="variable-depth-queries" class="position-relative d-flex align-items-center group"> Variable-Depth 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="variable-depth-queries" aria-haspopup="dialog" aria-label="Share link: Variable-Depth Queries"> Share link </button> </h4>Graph databases excel at queries where the depth of traversal isn’t known in advance: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Find all reporting relationships up the management chain MATCH (employee:Person {name: 'Alice'})-[:REPORTS_TO*]->(manager) RETURN manager.name, manager.title; -- Find shortest path between two people MATCH path = shortestPath( (a:Person {name: 'Alice'})-[:KNOWS*]-(b:Person {name: 'Zach'}) ) RETURN path; </code></pre></div>These queries are impractical or prohibitively expensive in relational databases. <h4 id="schema-flexibility" class="position-relative d-flex align-items-center group"> Schema Flexibility <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-flexibility" aria-haspopup="dialog" aria-label="Share link: Schema Flexibility"> Share link </button> </h4>Graph databases offer flexible schemas that can evolve: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Different types of entities coexist naturally CREATE (p:Person {name: 'Alice'}); CREATE (c:Company {name: 'Acme Corp'}); CREATE (pr:Product {name: 'Widget'}); -- Relationships can connect any nodes MATCH (p:Person {name: 'Alice'}), (c:Company {name: 'Acme Corp'}) CREATE (p)-[:WORKS_AT]->(c); MATCH (c:Company {name: 'Acme Corp'}), (pr:Product {name: 'Widget'}) CREATE (c)-[:PRODUCES]->(pr); -- Add new properties without migrations MATCH (p:Person {name: 'Alice'}) SET p.department = 'Engineering', p.start_date = date('2024-01-15'); </code></pre></div> <h3 id="graph-databases-vs-other-database-types" class="position-relative d-flex align-items-center group"> Graph Databases vs. Other Database 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="graph-databases-vs-other-database-types" aria-haspopup="dialog" aria-label="Share link: Graph Databases vs. Other Database Types"> Share link </button> </h3> <h4 id="vs-relational-databases-sql" class="position-relative d-flex align-items-center group"> vs. Relational Databases (SQL) <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="vs-relational-databases-sql" aria-haspopup="dialog" aria-label="Share link: vs. Relational Databases (SQL)"> Share link </button> </h4>Relational Databases (PostgreSQL, MySQL, Oracle): <ul> <li>Data Model: Tables with rows and columns</li> <li>Relationships: Foreign keys and JOINs</li> <li>Schema: Fixed schema with migrations</li> <li>Best For: Structured data, reporting, transactions on single entities</li> <li>Weak At: Many-to-many relationships, variable-depth queries</li> </ul> Graph Databases (Geode, Neo4j): <ul> <li>Data Model: Nodes and relationships</li> <li>Relationships: First-class, directly traversable</li> <li>Schema: Flexible, evolves with your application</li> <li>Best For: Connected data, pattern matching, relationship analysis</li> <li>Weak At: Aggregate calculations across entire dataset</li> </ul> When to Choose Graph: <ul> <li>Relationship queries are primary workload</li> <li>Need to traverse variable depths</li> <li>Data model evolves frequently</li> <li>Connections between entities are as important as the entities themselves</li> </ul> <h4 id="vs-document-databases-nosql" class="position-relative d-flex align-items-center group"> vs. Document Databases (NoSQL) <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="vs-document-databases-nosql" aria-haspopup="dialog" aria-label="Share link: vs. Document Databases (NoSQL)"> Share link </button> </h4>Document Databases (MongoDB, CouchDB): <ul> <li>Data Model: JSON/BSON documents</li> <li>Relationships: Embedded documents or references</li> <li>Query Style: Key-value lookups, nested object queries</li> <li>Best For: Hierarchical data, flexible schemas, read-heavy workloads</li> </ul> Graph Databases: <ul> <li>Data Model: Nodes and relationships</li> <li>Relationships: Bidirectional, multi-hop traversals</li> <li>Query Style: Pattern matching, path finding</li> <li>Best For: Interconnected data, relationship analysis</li> </ul> Example: Representing a blog with comments Document Database: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-json" data-lang="json">{ "post_id": "post1", "title": "Graph Databases are Great", "author": "Alice", "comments": [ {"user": "Bob", "text": "Great article!"}, {"user": "Carol", "text": "Very informative"} ] } </code></pre></div><ul> <li>Simple to query a post’s comments</li> <li>Difficult to find all comments by a user across all posts</li> <li>No representation of relationships between users</li> </ul> Graph Database: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">CREATE (alice:User {name: 'Alice'}); CREATE (post:Post {title: 'Graph Databases are Great'}); CREATE (bob:User {name: 'Bob'}); CREATE (comment:Comment {text: 'Great article!'}); CREATE (alice)-[:AUTHORED]->(post); CREATE (bob)-[:COMMENTED]->(comment); CREATE (comment)-[:ON_POST]->(post); </code></pre></div><ul> <li>Easy to find all posts by a user</li> <li>Easy to find all comments by a user</li> <li>Can explore user relationships through interactions</li> </ul> <h4 id="vs-key-value-stores" class="position-relative d-flex align-items-center group"> vs. Key-Value Stores <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="vs-key-value-stores" aria-haspopup="dialog" aria-label="Share link: vs. Key-Value Stores"> Share link </button> </h4>Key-Value Stores (Redis, DynamoDB): <ul> <li>Data Model: Simple key-value pairs</li> <li>Access Pattern: Direct key lookup, extremely fast</li> <li>Best For: Caching, session storage, simple data structures</li> </ul> Graph Databases: <ul> <li>Data Model: Complex connected structures</li> <li>Access Pattern: Pattern matching and traversals</li> <li>Best For: Relationship queries and analytics</li> </ul> Use Together: Key-value stores for caching, graphs for relationship modeling. <h3 id="common-graph-database-use-cases" class="position-relative d-flex align-items-center group"> Common Graph Database Use Cases <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-graph-database-use-cases" aria-haspopup="dialog" aria-label="Share link: Common Graph Database Use Cases"> Share link </button> </h3> <h4 id="social-networks" class="position-relative d-flex align-items-center group"> Social Networks <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-networks" aria-haspopup="dialog" aria-label="Share link: Social Networks"> Share link </button> </h4>Represent users, posts, likes, comments, and friendships: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Find mutual friends MATCH (me:User {id: 'user1'})-[:FRIENDS_WITH]-(mutual)-[:FRIENDS_WITH]-(them:User {id: 'user2'}) RETURN mutual.name; -- Suggest friends (friends of friends not yet connected) MATCH (me:User {id: 'user1'})-[:FRIENDS_WITH*2]-(suggested) WHERE NOT (me)-[:FRIENDS_WITH]-(suggested) AND suggested.id <> 'user1' RETURN suggested.name, count(*) as mutual_friends ORDER BY mutual_friends DESC; </code></pre></div> <h4 id="recommendation-engines" class="position-relative d-flex align-items-center group"> Recommendation Engines <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="recommendation-engines" aria-haspopup="dialog" aria-label="Share link: Recommendation Engines"> Share link </button> </h4>Collaborative filtering and content-based recommendations: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Product recommendations based on similar users MATCH (me:User {id: 'user1'})-[:PURCHASED]->(p:Product) MATCH (p)<-[:PURCHASED]-(similar:User)-[:PURCHASED]->(rec:Product) WHERE NOT (me)-[:PURCHASED]->(rec) RETURN rec.name, count(*) as score ORDER BY score DESC LIMIT 10; </code></pre></div> <h4 id="fraud-detection" class="position-relative d-flex align-items-center group"> 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="fraud-detection" aria-haspopup="dialog" aria-label="Share link: Fraud Detection"> Share link </button> </h4>Identify suspicious patterns in transactions and relationships: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Find accounts sharing suspicious attributes MATCH (a1:Account)-[:HAS_PHONE]->(phone:Phone)<-[:HAS_PHONE]-(a2:Account) MATCH (a1)-[:HAS_EMAIL]->(email:Email)<-[:HAS_EMAIL]-(a2) WHERE a1.id <> a2.id RETURN a1.id, a2.id, phone.number, email.address; -- Detect circular transaction patterns MATCH path = (a:Account)-[:TRANSFERRED_TO*3..5]->(a) WHERE all(r IN relationships(path) WHERE r.amount > 1000) RETURN path; </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>Represent complex domain knowledge and relationships: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Medical knowledge graph CREATE (disease:Disease {name: 'Type 2 Diabetes'}); CREATE (symptom:Symptom {name: 'Increased thirst'}); CREATE (treatment:Treatment {name: 'Metformin'}); CREATE (gene:Gene {name: 'TCF7L2'}); CREATE (disease)-[:HAS_SYMPTOM]->(symptom); CREATE (disease)-[:TREATED_WITH]->(treatment); CREATE (disease)-[:ASSOCIATED_WITH]->(gene); -- Query: What are treatment options for diseases associated with a gene? MATCH (gene:Gene {name: 'TCF7L2'})<-[:ASSOCIATED_WITH]-(disease)-[:TREATED_WITH]->(treatment) RETURN disease.name, collect(treatment.name) as treatments; </code></pre></div> <h4 id="network-and-it-operations" class="position-relative d-flex align-items-center group"> Network and IT Operations <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="network-and-it-operations" aria-haspopup="dialog" aria-label="Share link: Network and IT Operations"> Share link </button> </h4>Model network topology and dependencies: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Infrastructure dependencies CREATE (web:Server {name: 'web-server-1', type: 'nginx'}); CREATE (app:Server {name: 'app-server-1', type: 'nodejs'}); CREATE (db:Server {name: 'db-server-1', type: 'geode'}); CREATE (web)-[:DEPENDS_ON]->(app); CREATE (app)-[:DEPENDS_ON]->(db); -- Find all services impacted if a server goes down MATCH (failed:Server {name: 'db-server-1'})<-[:DEPENDS_ON*]-(impacted) RETURN impacted.name, impacted.type; </code></pre></div> <h3 id="core-graph-concepts" class="position-relative d-flex align-items-center group"> Core Graph 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-graph-concepts" aria-haspopup="dialog" aria-label="Share link: Core Graph Concepts"> Share link </button> </h3> <h4 id="directed-vs-undirected-relationships" class="position-relative d-flex align-items-center group"> Directed vs. Undirected 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="directed-vs-undirected-relationships" aria-haspopup="dialog" aria-label="Share link: Directed vs. Undirected Relationships"> Share link </button> </h4>Directed (most common in graph databases): <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">(alice)-[:FOLLOWS]->(bob) -- Alice follows Bob, but Bob doesn't follow Alice </code></pre></div>Undirected (represented as bidirectional): <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Create both directions for undirected relationships CREATE (a)-[:FRIENDS_WITH]->(b), (b)-[:FRIENDS_WITH]->(a); -- Or query ignoring direction MATCH (a:Person)-[:FRIENDS_WITH]-(b: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>Relationships can carry data: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">CREATE (alice)-[:KNOWS { since: 2020, strength: 'strong', met_at: 'University', interaction_count: 150 }]->(bob); -- Query using relationship properties MATCH (p:Person)-[k:KNOWS]->(f:Person) WHERE k.since >= 2020 AND k.strength = 'strong' RETURN p.name, f.name, k.met_at; </code></pre></div> <h4 id="multiple-labels" class="position-relative d-flex align-items-center group"> Multiple Labels <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="multiple-labels" aria-haspopup="dialog" aria-label="Share link: Multiple Labels"> Share link </button> </h4>Nodes can have multiple labels: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">CREATE (alice:Person:Employee:Manager { name: 'Alice', employee_id: 'E123', department: 'Engineering' }); -- Query using specific labels MATCH (m:Manager) RETURN m.name; MATCH (e:Employee) WHERE e.department = 'Engineering' RETURN count(e); </code></pre></div> <h4 id="path-queries" class="position-relative d-flex align-items-center group"> Path 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="path-queries" aria-haspopup="dialog" aria-label="Share link: Path Queries"> Share link </button> </h4>Find paths through the graph: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Shortest path MATCH path = shortestPath((a:Person {name: 'Alice'})-[:KNOWS*]-(z:Person {name: 'Zach'})) RETURN path; -- All paths up to length 5 MATCH path = (a:Person {name: 'Alice'})-[:KNOWS*1..5]-(connection) RETURN path; -- Paths matching complex patterns MATCH path = (p:Person)-[:WORKS_AT]->(c:Company)-[:PRODUCES]->(pr:Product) RETURN path; </code></pre></div> <h3 id="the-graph-query-language-gql" class="position-relative d-flex align-items-center group"> The Graph Query Language (GQL) <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="the-graph-query-language-gql" aria-haspopup="dialog" aria-label="Share link: The Graph Query Language (GQL)"> Share link </button> </h3> <h4 id="iso-standard" class="position-relative d-flex align-items-center group"> ISO Standard <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="iso-standard" aria-haspopup="dialog" aria-label="Share link: ISO Standard"> Share link </button> </h4>Geode implements ISO/IEC 39075:2024, the international standard for graph databases. This provides: <ul> <li>Standardization: Like SQL for relational databases</li> <li>Portability: Skills and queries transfer between compliant databases</li> <li>Maturity: Based on decades of graph database experience</li> <li>Future-Proof: Industry-backed standard ensures long-term support</li> </ul> <h4 id="key-gql-concepts" class="position-relative d-flex align-items-center group"> Key GQL 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="key-gql-concepts" aria-haspopup="dialog" aria-label="Share link: Key GQL Concepts"> Share link </button> </h4>Pattern Matching: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- The heart of GQL: matching patterns in the graph MATCH (p:Person)-[:WORKS_AT]->(c:Company) WHERE c.name = 'Acme Corp' RETURN p.name; </code></pre></div>Property Access: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Access node and relationship properties MATCH (p:Person) RETURN p.name, p.age, p.email; </code></pre></div>Filtering: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- WHERE clause for conditions MATCH (p:Person) WHERE p.age > 30 AND p.city = 'New York' RETURN p; </code></pre></div>Aggregation: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- COUNT, SUM, AVG, MIN, MAX MATCH (c:Company)<-[:WORKS_AT]-(e:Employee) RETURN c.name, count(e) as employee_count ORDER BY employee_count DESC; </code></pre></div> <h3 id="graph-database-benefits" class="position-relative d-flex align-items-center group"> Graph Database Benefits <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-database-benefits" aria-haspopup="dialog" aria-label="Share link: Graph Database Benefits"> Share link </button> </h3> <h4 id="performance" class="position-relative d-flex align-items-center group"> 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="performance" aria-haspopup="dialog" aria-label="Share link: Performance"> Share link </button> </h4>Relationship queries are O(1): <ul> <li>Following a relationship is a pointer lookup, not a table scan</li> <li>Performance doesn’t degrade with data size for connected queries</li> <li>Linear scaling for variable-depth traversals</li> </ul> Index-free adjacency: <ul> <li>Each node directly references its relationships</li> <li>No index lookups needed to traverse</li> <li>Constant-time relationship following</li> </ul> <h4 id="developer-productivity" class="position-relative d-flex align-items-center group"> Developer Productivity <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="developer-productivity" aria-haspopup="dialog" aria-label="Share link: Developer Productivity"> Share link </button> </h4>Natural modeling: <ul> <li>Graph structure mirrors how we think about connected data</li> <li>No impedance mismatch between model and database</li> <li>Visual representation aids understanding</li> </ul> Expressive queries: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Complex relationships expressed simply MATCH (user:User {id: 'user1'})-[:PURCHASED]->(product:Product) MATCH (product)<-[:PURCHASED]-(other:User)-[:PURCHASED]->(recommendation:Product) WHERE NOT (user)-[:PURCHASED]->(recommendation) RETURN DISTINCT recommendation LIMIT 10; </code></pre></div> <h4 id="flexibility" class="position-relative d-flex align-items-center group"> Flexibility <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="flexibility" aria-haspopup="dialog" aria-label="Share link: Flexibility"> Share link </button> </h4>Schema evolution: <ul> <li>Add new node types without altering existing data</li> <li>Add new relationship types as requirements evolve</li> <li>Add properties to nodes and relationships dynamically</li> </ul> Polyglot persistence: <ul> <li>Use graphs for connected data alongside other database types</li> <li>Complement relational databases for specific use cases</li> <li>Integrate with document stores, caches, and data warehouses</li> </ul> <h3 id="graph-database-challenges" class="position-relative d-flex align-items-center group"> Graph Database Challenges <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-database-challenges" aria-haspopup="dialog" aria-label="Share link: Graph Database Challenges"> Share link </button> </h3> <h4 id="when-not-to-use-graphs" class="position-relative d-flex align-items-center group"> When Not to Use 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="when-not-to-use-graphs" aria-haspopup="dialog" aria-label="Share link: When Not to Use Graphs"> Share link </button> </h4>High-volume aggregate operations: <ul> <li>Summing all sales across millions of records</li> <li>Statistical analysis on entire datasets</li> <li>Better served by columnar or relational databases</li> </ul> Simple key-value lookups: <ul> <li>Session storage, caching</li> <li>Better served by key-value stores like Redis</li> </ul> Hierarchical data without relationships: <ul> <li>Simple document structures</li> <li>Better served by document databases</li> </ul> Time-series data: <ul> <li>IoT sensor readings, logs</li> <li>Better served by time-series databases</li> </ul> <h4 id="learning-curve" class="position-relative d-flex align-items-center group"> Learning Curve <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="learning-curve" aria-haspopup="dialog" aria-label="Share link: Learning Curve"> Share link </button> </h4>Different thinking: <ul> <li>Requires shift from tabular thinking to graph thinking</li> <li>Pattern matching vs. SQL joins</li> <li>Understanding graph algorithms and traversals</li> </ul> Solution: Start with simple models, gradually add complexity as understanding grows. <h3 id="getting-started-with-graph-thinking" class="position-relative d-flex align-items-center group"> Getting Started with Graph Thinking <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="getting-started-with-graph-thinking" aria-haspopup="dialog" aria-label="Share link: Getting Started with Graph Thinking"> Share link </button> </h3> <h4 id="step-1-identify-entities-and-relationships" class="position-relative d-flex align-items-center group"> Step 1: Identify Entities and 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="step-1-identify-entities-and-relationships" aria-haspopup="dialog" aria-label="Share link: Step 1: Identify Entities and Relationships"> Share link </button> </h4>Example: Modeling an e-commerce system Entities (nodes): <ul> <li>Customers</li> <li>Products</li> <li>Orders</li> <li>Categories</li> <li>Vendors</li> </ul> Relationships: <ul> <li>Customer PLACED Order</li> <li>Order CONTAINS Product</li> <li>Product IN_CATEGORY Category</li> <li>Vendor SUPPLIES Product</li> </ul> <h4 id="step-2-add-properties" class="position-relative d-flex align-items-center group"> Step 2: Add 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="step-2-add-properties" aria-haspopup="dialog" aria-label="Share link: Step 2: Add Properties"> Share link </button> </h4>Nodes: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">(customer:Customer { id: 'C123', name: 'Alice', email: 'alice@example.com', join_date: date('2024-01-15') }) (product:Product { id: 'P456', name: 'Laptop', price: 1299.99, stock: 50 }) </code></pre></div>Relationships: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-[:PLACED { order_date: datetime('2024-03-15T10:30:00'), total_amount: 1299.99 }]-> -[:CONTAINS { quantity: 1, unit_price: 1299.99 }]-> </code></pre></div> <h4 id="step-3-define-queries" class="position-relative d-flex align-items-center group"> Step 3: Define 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="step-3-define-queries" aria-haspopup="dialog" aria-label="Share link: Step 3: Define Queries"> Share link </button> </h4>What questions do you need to answer? <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Customer purchase history MATCH (c:Customer {id: 'C123'})-[:PLACED]->(o:Order)-[:CONTAINS]->(p:Product) RETURN p.name, o.order_date; -- Products frequently bought together MATCH (p1:Product)<-[:CONTAINS]-(o:Order)-[:CONTAINS]->(p2:Product) WHERE p1.id = 'P456' AND p1.id <> p2.id RETURN p2.name, count(*) as frequency ORDER BY frequency DESC; -- Customer lifetime value MATCH (c:Customer {id: 'C123'})-[placed:PLACED]->(o:Order) RETURN sum(placed.total_amount) as lifetime_value; </code></pre></div> <h3 id="best-practices-for-beginners" class="position-relative d-flex align-items-center group"> Best Practices for Beginners <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="best-practices-for-beginners" aria-haspopup="dialog" aria-label="Share link: Best Practices for Beginners"> Share link </button> </h3> <h4 id="1-start-simple" class="position-relative d-flex align-items-center group"> 1. Start Simple <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="1-start-simple" aria-haspopup="dialog" aria-label="Share link: 1. Start Simple"> Share link </button> </h4>Begin with a small subset of your domain: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Phase 1: Basic entities CREATE (alice:User {name: 'Alice'}); CREATE (bob:User {name: 'Bob'}); CREATE (alice)-[:KNOWS]->(bob); -- Phase 2: Add properties SET alice.email = 'alice@example.com', alice.joined = date('2024-01-15'); -- Phase 3: Add more relationship types CREATE (alice)-[:FOLLOWS]->(bob); -- Phase 4: Expand the model CREATE (post:Post {content: 'Hello world!'}); CREATE (alice)-[:POSTED]->(post); </code></pre></div> <h4 id="2-use-meaningful-names" class="position-relative d-flex align-items-center group"> 2. Use Meaningful Names <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="2-use-meaningful-names" aria-haspopup="dialog" aria-label="Share link: 2. Use Meaningful Names"> Share link </button> </h4><div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Good: Clear, descriptive names CREATE (user:User {name: 'Alice'})-[:PURCHASED {date: date('2024-03-15')}]->(product:Product {name: 'Laptop'}); -- Bad: Unclear abbreviations CREATE (u:U {n: 'Alice'})-[:P {d: '2024-03-15'}]->(pr:Pr {n: 'Laptop'}); </code></pre></div> <h4 id="3-create-indexes-early" class="position-relative d-flex align-items-center group"> 3. Create Indexes Early <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="3-create-indexes-early" aria-haspopup="dialog" aria-label="Share link: 3. Create Indexes Early"> 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 CONSTRAINT unique_user_id ON :User(id); </code></pre></div> <h4 id="4-visualize-your-model" class="position-relative d-flex align-items-center group"> 4. Visualize Your 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="4-visualize-your-model" aria-haspopup="dialog" aria-label="Share link: 4. Visualize Your Model"> Share link </button> </h4>Draw your graph model before implementing: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-fallback" data-lang="fallback">[User] -PURCHASED-> [Order] -CONTAINS-> [Product] | | +-REVIEWED----------------------------->+ </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>Getting Started: Practical guides to begin using Geode</li> <li>Graph Modeling: Design patterns and modeling techniques</li> <li>Query Language: Deep dive into GQL syntax and features</li> <li>Examples: Practical code samples and applications</li> <li>Use Cases: Industry-specific graph database applications</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: Understanding the theoretical foundation</li> <li>Graph Algorithms: PageRank, community detection, shortest paths</li> <li>GQL Standard: ISO/IEC 39075:2024 specification details</li> <li>Performance: How graph databases achieve efficiency</li> <li>Architecture: How Geode implements graph database concepts</li> </ul> <hr> Graph databases provide a natural, efficient way to model and query connected data. By understanding the fundamental concepts of nodes, relationships, and properties, you can leverage graph databases for applications where relationships are as important as the entities themselves. Geode’s ISO 100% GQL compliance makes graph databases accessible and powerful for modern applications.

Popular

Related Articles

Data Model and Types

Introduction and Key Features

Transactions and Data Integrity