Need advice about which tool to choose?Ask the StackShare community!
Dgraph vs Neo4j: What are the differences?
Key Differences between Dgraph and Neo4j
Dgraph and Neo4j are two popular graph databases with some key differences.
1. Data Sharding: Dgraph automatically shards data across multiple servers, allowing for efficient horizontal scaling. On the other hand, Neo4j does not have built-in support for data sharding, requiring manual distribution of data across different instances.
2. Query Language: Dgraph uses GraphQL+- as its query language, which enables developers to write expressive and efficient queries with complex filtering and aggregations. Neo4j, on the other hand, uses the Cypher query language, which is specifically designed for querying graph databases.
3. Architecture: Dgraph follows a distributed architecture, where data is distributed across multiple servers, providing high availability and fault tolerance. In contrast, Neo4j follows a single-server architecture, where all data is stored on a single instance.
4. ACID Compliance: Dgraph is designed to be eventually consistent, focusing more on horizontal scalability and performance, while sacrificing full ACID (Atomicity, Consistency, Isolation, Durability) compliance. Neo4j, on the other hand, offers strong consistency and full ACID compliance out of the box.
5. JSON-based Data Model: Dgraph natively supports a JSON-based data model, allowing for flexible and dynamic schema-less data storage. Neo4j uses a property graph model, where data is represented as nodes connected by relationships, providing more rigid schema enforcement.
6. Community and Ecosystem: While both Dgraph and Neo4j have active communities, Neo4j has a larger and more established ecosystem. Neo4j has been around for a longer time and has a wider range of community-contributed extensions and integrations.
In summary, Dgraph and Neo4j differ in terms of data sharding, query language, architecture, ACID compliance, data model, and ecosystem. Dgraph focuses on scalability and performance with automatic data sharding and a flexible JSON-based data model, while Neo4j offers strong consistency, ACID compliance, and a more established ecosystem.
Hi, I want to create a social network for students, and I was wondering which of these three Oriented Graph DB's would you recommend. I plan to implement machine learning algorithms such as k-means and others to give recommendations and some basic data analyses; also, everything is going to be hosted in the cloud, so I expect the DB to be hosted there. I want the queries to be as fast as possible, and I like good tools to monitor my data. I would appreciate any recommendations or thoughts.
Context:
I released the MVP 6 months ago and got almost 600 users just from my university in Colombia, But now I want to expand it all over my country. I am expecting more or less 20000 users.
I have not used the others but I agree, ArangoDB should meet your needs. If you have worked with RDBMS and SQL before Arango will be a easy transition. AQL is simple yet powerful and deployment can be as small or large as you need. I love the fact that for my local development I can run it as docker container as part of my project and for production I can have multiple machines in a cluster. The project is also under active development and with the latest round of funding I feel comfortable that it will be around a while.
Hi Jaime. I've worked with Neo4j and ArangoDB for a few years and for me, I prefer to use ArangoDB because its query sintax (AQL) is easier. I've built a network topology with both databases and now ArangoDB is the databases for that network topology. Also, ArangoDB has ArangoML that maybe can help you with your recommendation algorithims.
Hi Jaime, I work with Arango for about 3 years quite a lot. Before I do some investigation and choose ArangoDB against Neo4j due to multi-type DB, speed, and also clustering (but we do not use it now). Now we have RMDB and Graph working together. As others said, AQL is quite easy, but u can use some of the drivers like Java Spring, that get you to another level.. If you prefer more copy-paste with little rework, perhaps Neo4j can do the job for you, because there is a bigger community around it.. But I have to solve some issues with the ArangoDB community and its also fast. So I will preffere ArangoDB... Btw, there is a super easy Foxx Microservice tool on Arango that can help you solve basic things faster than write down robust BackEnd.
Pros of Dgraph
- Graphql as a query language is nice if you like apollo3
- Easy set up2
- Low learning curve2
- Open Source1
- High Performance1
Pros of Neo4j
- Cypher – graph query language70
- Great graphdb61
- Open source33
- Rest api31
- High-Performance Native API27
- ACID23
- Easy setup21
- Great support17
- Clustering11
- Hot Backups9
- Great Web Admin UI8
- Powerful, flexible data model7
- Mature7
- Embeddable6
- Easy to Use and Model5
- Best Graphdb4
- Highly-available4
- It's awesome, I wanted to try it2
- Great onboarding process2
- Great query language and built in data browser2
- Used by Crunchbase2
Sign up to add or upvote prosMake informed product decisions
Cons of Dgraph
Cons of Neo4j
- Comparably slow9
- Can't store a vertex as JSON4
- Doesn't have a managed cloud service at low cost1
Sign up to add or upvote consMake informed product decisions
What is Dgraph?
What is Neo4j?
Need advice about which tool to choose?Ask the StackShare community!
What companies use Neo4j?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Dgraph?
What tools integrate with Neo4j?
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+37