Modelling data in ArangoDB vs MongoDB - Tutorial

Sign up for ArangoGraph Insights Platform

Before signing up, please accept our terms & conditions and privacy policy.

What to expect after you signup
You can try out ArangoDB Cloud FREE for 14 days. No credit card required and you are not obligated to keep using ArangoDB Cloud.

At the end of your free trial, enter your credit card details to continue using ArangoDB Cloud.

If you decide that ArangoDB Cloud is not (yet) for you, you can simply leave and come back later.

ACCEPT

MongoDB to ArangoDB Tutorial

Modelling data in ArangoDB vs MongoDB

This is a short tutorial showing you the comparison between performing queries in ArangoDB and MongoDB.

Both, ArangoDB and MongoDB, are “NoSQL databases” and might look pretty similar at first glance. When it comes to data modelling and data querying, they are somewhat different. The main difference being ArangoDB’s flexibility and functionality when working with graph data.  In this 10 min tutorial we will show the differences in syntax between the two databases. We will have a look at some simple examples, but also touch base with a few more complex ones.

Note: Before we start make sure that you have both, ArangoDB 3.0 and MongoDB 3.2, databases installed.

Let's get started

For this tutorial we are going to use two collections of data that are bundled in ArangoDB: worldVertices and worldEdges.

To have the same datasets in both databases, we need to first dump the data from ArangoDB:

Using arangodump will export the raw data including some metadata which you could feed into another ArangoDB instance right away. However, to load the data into MongoDB we need to have the raw data without ArangoDB specific metadata. To extract the raw data we are using the jq tool. The raw data is contained within the _data key in the dump file.

Note: Make sure that you have jq command available on your machine before the import.

and import it into MongoDB:

Now that you are all set, we can start with some query examples.

Find a document

The following query finds the first document matching a filter criteria. In the example below we are searching for the first document where the type is “country”. We don’t specify any sorting neither in MongoDB nor in ArangoDB, therefore the results are more or less random in both cases.

MongoDB

ArangoDB

The results will approximately look like this:

Find a list of documents

With the following query you will find all documents matching a set-up criteria. In this case all documents where type is “continent” will be displayed.

MongoDB

ArangoDB

The results should look like something like this:

Update documents

Here we are going to update all documents that match a filter “type: country” with a “population: 10″.

MongoDB

ArangoDB

And the results that you will see:

Now that we have executed the query, let’s check if the update took place. For simplicity we are going to list one document that got updated.

Find a document:

The results that you will see will look like this:

Note: Now that we have covered some simple steps, we are going to move on to a few more complex examples. Here we are going to use ArangoDB’s powerful & versatile SQL-like query language – AQL – for the first time.

Aggregate

Below is an example of how to use the aggregate function in both databases. Here we are going to group all documents in the worldVertices collection by their type and display what amount of population each type has.

MongoDB

ArangoDB

The results will look like something like this:

Aggregate with a filter

The below example shows how to use the aggregate function with a filter. Here we will group all documents in the worldVertices collection by type, list the amount of population each type has, but by using the filter we will only see the result for type: “country”.

MongoDB

ArangoDB

You will see the following results:

Range select

With the range select function we are going to filter all documents in the worldVertices collection where the name range is between “Bul” and “Cb”.

MongoDB

ArangoDB

Your results will be like this:

JOINs

With the following example we are going to do a JOIN between two documents in two collections (worldVertices and worldEdges). We will find out what the capital of Australia is.

MongoDB

ArangoDB

The results will look like this:

Graph Queries:
What you can do with ArangoDB and cannot do with MongoDB

While querying the immediate connection in the graph (country to capital) is still doable via JOINs (previous examples above) it can rather quickly become more difficult once you dig deeper into the graph and perform more complex queries.

As the nature of our example data is a graph and ArangoDB is also a graph database, we can show you with the example below how this procedure can be done in an easier and neater way. In this case, ArangoDB offers more flexibility in comparison to MongoDB.

MongoDB

–

ArangoDB

Delete a set of documents

As the final step of this quick tutorial, we are going to delete a set of documents based on a filter – document type is “capital”.

MongoDB

First, count the documents in a collection:

ArangoDB

The results should look like this:

Delete documents:

The results will be the following:

Count the documents again to check:

And the results should be:

Learn more

By now you should have a sound understanding of how to run some operations in ArangoDB in comparison to MongoDB. But there is much more to know and so much more you can do: