Neo4j Aura (Annual)
Neo4jExternal reviews
135 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Easy to learn, sophisticated features
What do you like best about the product?
Sophisticated features
Lesser Maintenance overhead for smaller data size
Gives a good ui to analyse data
Lesser Maintenance overhead for smaller data size
Gives a good ui to analyse data
What do you dislike about the product?
graphical representation for complex graph is not great
What problems is the product solving and how is that benefiting you?
GC pauses
Great data store. Very use case specific. Not recommended for users not operating at scale.
What do you like best about the product?
I started using Neo4J to represent various facilities ( of a startup that I work at) across the city as nodes and represent their relationships in terms of mode of commute available and the associated costs.
The brilliant thing about Neo4J, or graph DB for that matter of fact, is that it represents a graph like database as a graph and not a format manipulated to be used like a graph. This is turn makes it extremely practical for various graph based use cases like route optimization, connectivity networks etc
One more added advantage with using neo4j is the ability to use years of research done on graphs & its algorithms.
Now, what sets neo4J apart :
1) The cypher query language is very natural to write and easy to understand.
2) Allows many RDBMS like constraints to be applied to a graph.
3) The in-built query browser eliminates the use of 3rd party tools for simple graph visualizations
The brilliant thing about Neo4J, or graph DB for that matter of fact, is that it represents a graph like database as a graph and not a format manipulated to be used like a graph. This is turn makes it extremely practical for various graph based use cases like route optimization, connectivity networks etc
One more added advantage with using neo4j is the ability to use years of research done on graphs & its algorithms.
Now, what sets neo4J apart :
1) The cypher query language is very natural to write and easy to understand.
2) Allows many RDBMS like constraints to be applied to a graph.
3) The in-built query browser eliminates the use of 3rd party tools for simple graph visualizations
What do you dislike about the product?
1) Not optimized for long traversal queries. Queries that require multiple routes inherently.
2) Very few DB drivers available, mostly are SDKs wrapped over the cypher query language (and communicates with the DB over HTTP & hence slightly slower).
3) cypher queries though simple to get started with, quickly turns into a complicated one due to very few methods.
2) Very few DB drivers available, mostly are SDKs wrapped over the cypher query language (and communicates with the DB over HTTP & hence slightly slower).
3) cypher queries though simple to get started with, quickly turns into a complicated one due to very few methods.
What problems is the product solving and how is that benefiting you?
We were trying to create a graph of various facilities and depots with weighted routes. What we essentially wanted to do was find the cheapest route from one facility to another ( via multiple hops)
Benefits of using neo4j are pretty obvious for us, we have created a graph and neo4j is a graph db, so there can not be a more natural fit for our usecase.
Benefits of using neo4j are pretty obvious for us, we have created a graph and neo4j is a graph db, so there can not be a more natural fit for our usecase.
Recommendations to others considering the product:
Just one : It doesn't scale with multiple cores if you are using the community edition.
So before using it in a production environment make sure that the community edition would meet your scale, as the enterprise edition is pretty steeply priced.
So before using it in a production environment make sure that the community edition would meet your scale, as the enterprise edition is pretty steeply priced.
A database to store elements of industrial system as vertexes and relationships among them as edges.
What do you like best about the product?
The query language - similar to other query languages.
The visual representation - No extra pain in visualizing data.
The visual representation - No extra pain in visualizing data.
What do you dislike about the product?
Initial learning curve. poor documentation. integration with C# environment.
Documentation for neo4jclient for c# is pathetic.
Documentation for neo4jclient for c# is pathetic.
What problems is the product solving and how is that benefiting you?
Impact Analysis is being automated.
Recommendations to others considering the product:
Strong community, FB,Goog and author biggie support.
Graph database with a powerful query language
What do you like best about the product?
Relatively easy installation, and a wide variety of language-specific integration libraries. The query language is concise and extremely powerful. What would have been done with a ton of loops and a variety of control statements was summed up in just a couple of lines. The syntax, while not as beautifully readable as many of the ruby/rails and nodejs code out there today, is readily understandable to others reviewing it, through as with anything the devil is in the details.
What do you dislike about the product?
The query language, while extremely powerful, can be a bit obtuse for complex queries. Additionally, if you're running something really sophisticated, you'll need some pretty solid hardware that can support it. In our case it was worth the benefit, but I could see someone using a much simpler solution using a relational database and less resources. Testing the queries also became problematic as we ended up tracing through our complex datastore by hand many times.
What problems is the product solving and how is that benefiting you?
We use neo4j in a service that recommends mobile apps based on a fairly complex set of criteria, but at the base of it, the algorithm finds similar users to the target and picks apps that have not yet been installed in certain content verticals. After a few hours of iterating on a solution, our algorithm came down to just few lines of neo4j query language.
Recommendations to others considering the product:
As with most implementations, start with small examples and build on it little by little.
showing 11 - 14