Просмотр кода страницы Why Graph Databases Are Perfect for Modern Data Challenges

When looking for a solution for your project, it is important to understand what makes each technology unique, what sets it apart. With ArangoDB that is its native multi-model approach including full graph database capabilities and I am going to explain the fundamental pieces of what that means.

Using ArangoDB as a Graph Database

If you are already familiar with the graph database concept, then you know that a graph consists of vertices (or nodes) connected via edges. Graph databases usually store edges connected to vertices directly at the vertex object. In ArangoDB this is handled differently (if you want to take a technical deep dive into ArangoDB’s approach, see this article).

Today, we will take a look at how ArangoDB let’s you map graph data natively to the database and how the database provides efficient access [https://arangodb.com/2022/07/what-is-a-graph-database/ graph database] to graph datasets with a variety of different access patterns like traversals, shortest path or pattern matching.

Vertices (or nodes) are being stored in normal collections. The key to graph database capabilities comes from something called, an edge collection and an edge index.

Let’s take a quick look at storing vertices and then explore a bit more on edge collections and indices.

Vertex Collections

To showcase the benefits of using graphs with ArangoDB we will use the example of domestic flights in the USA. The dataset describes the relationship of airports (vertices) and the flights (edges) between them. We use the same dataset in our Graph Course for Beginners

The airports collection is a normal collection of JSON documents and requires nothing special or out of the ordinary to work with a graph. Please note the _id attribute, as this will play a crucial role for our graph.

We will explore these documents a bit more in a moment, for now though, just understand that our airports collection contains normal JSON documents that represent airports.

The Edge Collection

To explain what an edge collection is, let’s start with a simple explanation of it; a special collection of JSON documents that describe the connection between two other documents.

Pretty simple right? Well, I have some good news, it actually is that simple. The power of native multi-model in ArangoDB is that edges stored in an edge collection are not tied to vertices stored in another collection, but can be stored and distributed independently – providing advantages in terms of data modeling flexibility and, most importantly, horizontal scalability.

Let’s go a little deeper here and take a look at what exactly, “describing the connection between two other documents” looks like.

A document in an Edge Collection will always contain at least five attributes. Those attributes are _id, _key, _rev, _to, and _from. The ‘magic’ comes from the _to and _from attributes. These two attributes define the beginning and end points for the edge, they are the _id attributes of the vertices that they connect to.

In our airports and flights example, airports are the vertices and flights ‘connect’ the airports with one another and therefore are the edges of our graph.