> ## Documentation Index
> Fetch the complete documentation index at: https://helix-claude-document-return-objects-rxi6v.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# What is a Graph Database?

> Learn how graph databases store and connect data using nodes and relationships

A graph database is a type of database that stores data using a graph structure, where information is represented through **nodes** (data points) and **edges** (relationships between nodes). Unlike traditional databases that use tables or documents, graph databases excel at managing highly connected data and complex relationships.

## How do graph databases work?

Graph databases store data using two fundamental concepts:

1. **Nodes** - These are the entities or objects in your data (like people, products, or locations)
2. **Edges** (or relationships) - These are the connections between nodes that describe how they relate to each other

### Example Structure

```mermaid theme={null}
graph LR
    A[Person: John] -->|FRIENDS_WITH| B[Person: Sarah]
    B -->|WORKS_AT| C[Company: Tech Corp]
    A -->|LIKES| D[Product: Laptop]
    B -->|PURCHASED| D
```

In this simple example:

* Nodes represent people, companies, and products
* Edges show relationships like friendships, employment, and product interactions
* Both nodes and edges can have properties (additional data attributes)

## What are graph databases used for?

### 1. Social Networks

Perfect for modeling:

* Friend connections
* Content sharing
* User interactions
* Community detection

### 2. Recommendation Engines

Excellent for:

* Product recommendations
* Content suggestions
* "People you may know" features
* Interest-based matching

### 3. Fraud Detection

Ideal for:

* Pattern recognition in financial transactions
* Identifying suspicious relationships
* Risk assessment
* Network analysis

### 4. Knowledge Graphs

Great for:

* Semantic search
* Data integration
* AI and machine learning
* Research and discovery

## When should I use a graph database?

Use a graph database when:

* Your data has many interconnected relationships
* You need to perform complex queries involving multiple relationships
* Pattern matching and path finding are important
* Traditional SQL joins become too complex or slow
* You need to model and query hierarchical structures

## What are the benefits of graph databases?

1. **Performance**: Faster for relationship-heavy queries
2. **Flexibility**: Easier to modify and extend the data model
3. **Intuitive**: More natural way to model connected data
4. **Scalability**: Better handling of complex relationship patterns

## Next steps

<CardGroup cols={2}>
  <Card title="What is HelixDB?" icon="database" href="/documentation/getting-started/helixdb">
    Learn about HelixDB's architecture and features
  </Card>

  <Card title="Getting started" icon="rocket" href="/documentation/cli-v2/getting-started">
    Install and deploy your first graph database
  </Card>

  <Card title="Social network guide" icon="users" href="/guides/social-network">
    Build a social network with graph databases
  </Card>

  <Card title="HelixQL basics" icon="book-open" href="/documentation/hql/hql">
    Learn to query graph data
  </Card>
</CardGroup>