Need advice about which tool to choose?Ask the StackShare community!

ArangoDB

206
294
+ 1
177
Neo4j

869
951
+ 1
320
Add tool

ArangoDB vs Neo4j: What are the differences?

ArangoDB: A distributed open-source database with a flexible data model for documents, graphs, and key-values. A distributed free and open-source database with a flexible data model for documents, graphs, and key-values. Build high performance applications using a convenient SQL-like query language or JavaScript extensions; Neo4j: The world’s leading Graph Database. Neo4j stores data in nodes connected by directed, typed relationships with properties on both, also known as a Property Graph. It is a high performance graph store with all the features expected of a mature and robust database, like a friendly query language and ACID transactions.

ArangoDB can be classified as a tool in the "Databases" category, while Neo4j is grouped under "Graph Databases".

Some of the features offered by ArangoDB are:

  • multi-model nosql db
  • acid
  • transactions

On the other hand, Neo4j provides the following key features:

  • intuitive, using a graph model for data representation
  • reliable, with full ACID transactions
  • durable and fast, using a custom disk-based, native storage engine

"Grahps and documents in one DB" is the top reason why over 24 developers like ArangoDB, while over 55 developers mention "Cypher – graph query language" as the leading cause for choosing Neo4j.

ArangoDB and Neo4j are both open source tools. It seems that ArangoDB with 8.22K GitHub stars and 576 forks on GitHub has more adoption than Neo4j with 6.6K GitHub stars and 1.63K GitHub forks.

According to the StackShare community, Neo4j has a broader approval, being mentioned in 114 company stacks & 47 developers stacks; compared to ArangoDB, which is listed in 11 company stacks and 15 developer stacks.

Pros of ArangoDB
Pros of Neo4j
  • 32
    Grahps and documents in one DB
  • 25
    Intuitive and rich query language
  • 23
    Good documentation
  • 22
    Open source
  • 18
    Joins for collections
  • 15
    Foxx is great platform
  • 14
    Great out of the box web interface with API playground
  • 6
    Low maintenance efforts
  • 6
    Clustering
  • 6
    Good driver support
  • 5
    Easy microservice creation with foxx
  • 3
    You can write true backendless apps
  • 2
    Managed solution available
  • 65
    Cypher – graph query language
  • 55
    Great graphdb
  • 31
    Open source
  • 29
    Rest api
  • 27
    High-Performance Native API
  • 21
    ACID
  • 19
    Easy setup
  • 14
    Great support
  • 10
    Clustering
  • 8
    Hot Backups
  • 7
    Powerful, flexible data model
  • 7
    Great Web Admin UI
  • 5
    Embeddable
  • 5
    Mature
  • 4
    Easy to Use and Model
  • 3
    Highly-available
  • 3
    Best Graphdb
  • 2
    It's awesome, I wanted to try it
  • 2
    Used by Crunchbase
  • 2
    Great query language and built in data browser
  • 1
    Great onboarding process

Sign up to add or upvote prosMake informed product decisions

Cons of ArangoDB
Cons of Neo4j
  • 3
    Web ui has still room for improvement
  • 2
    No support for blueprints standard, using custom AQL
  • 4
    Can't store a vertex as JSON
  • 3
    Comparably slow

Sign up to add or upvote consMake informed product decisions