Neo4j Aura (Annual)
Neo4jExternal reviews
139 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Neo4j ,a perfect fit graph database for creating any kind of social network structure
What do you like best about the product?
1)Ease of use
2)Speed of graph traversal
3)Interactive console
2)Speed of graph traversal
3)Interactive console
What do you dislike about the product?
Sorting is expensive in terms of performance.
Scaling is an issue once the data exceeds certain limits
Scaling is an issue once the data exceeds certain limits
What problems is the product solving and how is that benefiting you?
We had created a social network for trading wherein traders can follow other traders and chk on their tips and trades.with an option to like .In terms of benefits it is certainly easier to have a graph database like neo4j doing heavy lifting of creating nodes and relationships rather than do it yourself in an rdbms
Recommendations to others considering the product:
If the business problem you are trying to solve, requires some form of complex hierarchies or a social network like structure or any other form of a network with multiple nodes and complex relationships, be sure to check on Neo4j, it will help you reduce the complexity of the model to a very large extent
Neo4j for ontology based KB generation
What do you like best about the product?
I've used neo4j for ontology-based KB generation task. So far, I have found neo4j graph-based data representation to be the best fit for such tasks. Apart from that, neo4j easy to learn and operate with.
What do you dislike about the product?
Neo4j master-slave architecture, writes are always done on master. Overall write-performance issues relative to SQL databases. Garbage collection pauses.
What problems is the product solving and how is that benefiting you?
I've used neo4j for the ontology-based KB generation task. The knowledge base consists of health care data with ontology representation as disease, symptoms, medication, organ/part of body associated etc along with their respective data and their relationship with each other. applying different graph-ml algorithm (like decision trees) on available data in graph to get a good accuracy of diagnosis. This also focuses on Knowledge Validation, Inferencing and Explanation/ Justification process of knowledge Engineering to maintain our healthcare knowledge base. Currently, we do not have CCDA’s available with information of symptom of patients (chief complaint, the reason for visit, etc.). For the time being, we are collecting data from online sources and will use that to symptom-based disease diagnosis.Healthcare KB generation of clinical data using cTAKES NLP and Neo4j.
As name of the project suggests "all men must serve", demo code of the project is available publically in the link. So far, I have found neo4j graph based data representation to be the best fit for such tasks.
As name of the project suggests "all men must serve", demo code of the project is available publically in the link. So far, I have found neo4j graph based data representation to be the best fit for such tasks.
Recommendations to others considering the product:
If you think your problem can be solved by graph based data, neo4j is worth a try
Rich community, robust and scalable
What do you like best about the product?
Very good interactive UI. very efficient on large datasets to support the multiple relations between the nodes.
What do you dislike about the product?
Sometimes hard to visualize complex data analyses. Automatic backups could be improved
What problems is the product solving and how is that benefiting you?
IoT device simulation and visualization.
Neo4J review
What do you like best about the product?
I like a lot trying to improve graph language
What do you dislike about the product?
For a moment now all thing that I like a lot
What problems is the product solving and how is that benefiting you?
It's helping to build fast graph databases
Easiest way to find connections in a schema-free database
What do you like best about the product?
Finding paths between nodes and doing what sql cannot
What do you dislike about the product?
Import function from csv files; creatina connections with cypher language
What problems is the product solving and how is that benefiting you?
Finding connections between data that where non treatable with traditional sql queries
Build large multi-property objects
What do you like best about the product?
In Neo4J, the various interactions between nodes are very effective in large databases. Processes are special keys that can be introduced into Neo4J to allow specific software requests or integration with Java operations. Also, UI client credentials restricted access enables for nicely controlled access. Neo4J is really helpful when it comes to solving the Cypher scripting language's limitations.
What do you dislike about the product?
Even the graphical display of the less advanced data set is nice, but it is not nice for a complex information set with over ten probable relationship charts. Also, you must use Neo4J native API, as it does not cooperate with any other open source APIs. I would specially like it to be integrate with BluePrint.
What problems is the product solving and how is that benefiting you?
Neo4J is a good choice for us to examine and create a relationship modules. It allows us to build large multi-property objects, consume them at competitive prices, scan for the map and display results quickly enough for you to actually operate the site from them. As the software is entirely materialized, both joints are assembled in frequent time, which significantly improves database quality without requiring additional software development.
Recommendations to others considering the product:
Neo4J is suitable for companies where matching information patterns is important and when data scanning constantly required. The use of Neo4J facilitates effective information processing and the capacity to search using Cypher. However, Neo4J is probably not really the most effective solution if you have deep requirements to search for individual nodes and their related data.
Speed up your business growth with Neo4J
What do you like best about the product?
Neo4J is a very fast software. It offers support for REST API, which allows for a simpler and quicker communication with Neo4J. Also, it offers a fantastic free version for the community that works with small projects. In general, Neo4J offers a wonderful user experience for every kind of data study you perform.
What do you dislike about the product?
The aggregation request needs a better support, as right now it is deficient. To be honest, I think most of the Neo4J issues comes with the support, so the solution would be to improve it. Also, I think Sandboxing should be easier too, as the process is unnecessarily complicated. If you work with a JSON data framework, it can not be changed into a graph.
What problems is the product solving and how is that benefiting you?
Neo4J introduces the foundation for our web host to collate supply chains of businesses. It is used by the development team of our IT department, but it benefits the entire company, as it allows us to speed up our business growth. Neo4J also involves more than a dozen node-to-node connections, which makes it perfect to be our primary software server.
Recommendations to others considering the product:
Neo4J is very good for POC and research purposes, even for very active querying language for database information in certain large databases. It is a good alternative option, as it's a challenging and expensive process to design this sort of information with a conventional SQL database. However, this is less ideal for any data structure different to graphs.
Build your information map with Neo4J
What do you like best about the product?
Neo4j has a very straightforward and simple to use Cypher language. This Cypher is quite good if pattern matches on the introduction of interesting ideas. It makes us replicate our thoughts even better, because the way we think of information is a very simple, with just nodes and connections and Neo4j helps us to show it exactly how it is. Also, Spark controls are used to do ML or more computer work, and you can boost file backups.
What do you dislike about the product?
The language framework support currently is only available on Java libraries. I would like to see more variety on this field.
What problems is the product solving and how is that benefiting you?
We use Neo4j to build our information map as a database system with no schema. We wanted a solution that could manage highly complicated queries without sacrificing quality, and Neo4j actually tackles these challenges. I evaluated it and compared it with similar usage cases and found that Neo4j performance was what we needed. The system was built to assign a node or an edge for each bit of information, so we did not have to use some kind of link server or any database without SQL.
Recommendations to others considering the product:
Neo4j is very useful for every enterprise concerned with complex and intertwined information. Also, it is suitable if you have your information represented as a graph, in nodes or edges, and if your network attributes are of concern to you. Nonetheless, it's not a good option if you need to work with a large, complex data collection.
Graph analysis with Neo4J
What do you like best about the product?
Neo4j is the leader in the graph databases solutions. Its initial release was in 2007 and today it must be the first solution if you want to do serious things with graphs and machine learning using very optimized algorithms. It's very polished in many features, including their web UI which is awesome. Cypher is also an awesome query language that gives "out-of-the-box" many algorithms that you'll usually have to do manually in Gremlin.
What do you dislike about the product?
Its licensing is GPL3 and their "Enterprise" edition is quite expensive. Community Edition (free) has lot less pro features than enterprise but usually you won't need them in "small" projects. Its scalability is also not specially friendly forcing you a master-slave with a load balancer. Cypher, althought very powerful, is a new query language to learn and that takes some time to master.
What problems is the product solving and how is that benefiting you?
Neo4J is specially good for rapid queries, graph analysis, sentiment analysis, prediction and to "make triangles" in general. We use it for a dependency graph and work flawlessly but we finally give a try to OrientDB to gain some know-how and make a comparison. Today we stay with Neo4j.
Recommendations to others considering the product:
The three players today are Neo4j, OrientDB and TitanDB. I would start with Neo4j as it's the one that has more tutorials and videos on internet. Then I would give a try to OrientDB after a while with Neo4j, just to know your options. Finally, if you really have a huge amount of data, try TitanDB from the beginning (deployment is complex).
Very interesting library with good support
What do you like best about the product?
The dashboard interface is really nice. Really user friendly to write Cypher queries to retrieve graph subsets. The graph is also made interactive and this helps easy presentation.
What do you dislike about the product?
There could be more flexible implementations of algorithms in the library. This is possible, but usually with the loss of readability.
What problems is the product solving and how is that benefiting you?
I was trying to compare two huge xml files. Initially I tried a DOM parser. But comparing files of the size >1GB eats up my memory and would never work. I did not want to introduce the overhead of a relational database. Using neo4j, I was able to create a library which transforms an xml to a graph in neo4j. This helps traversal and retrieval
Recommendations to others considering the product:
Just play around with the interface, the bouncing nodes and relationships. This is the easiest way to get familiar with Cypher.
Understand graph algorithms before attempting to use the built in methods in neo4j. This will save a lot of time as it is difficult to map the interfaces with the familiar algorithms.
Understand graph algorithms before attempting to use the built in methods in neo4j. This will save a lot of time as it is difficult to map the interfaces with the familiar algorithms.
showing 51 - 60