Neo4j Enterprise Edition
Neo4j | 5.xLinux/Unix, Amazon Linux 2023.1.20230719 - 64-bit Amazon Machine Image (AMI)
External reviews
External reviews are not included in the AWS star rating for the product.
Forward thinking product alas not always practical.
What do you like best about the product?
Property graph model is great as it is isomorphic to datastructures (knowledge graphs) that we model which lets us avoid writing much glue code and awful joins. I very much like the query language for its flexibility and of course the web interface is super useful for exploration.
What do you dislike about the product?
I wish there was some room for hybrid representation - like in document-based dbs. In some cases, the fact that it's a connected graph rather than a collection of ad-hoc rows, triples or whatever puts additional responsibility in certain fairly basic use cases.
What problems is the product solving and how is that benefiting you?
Knowledge representation and cognitive memory modeling for natural language understanding / artificial intelligence.
Recommendations to others considering the product:
I've seen an earlier version few years back and witnessed witnessed how it matured, especially the UI. But be wary that it might not work in plain old object serialization use-cases (although I know there is a great object persistence framework for Neo - NeoModel). It should be great for exploratory applications like social network analysis but at the same time it would accommodate something more profound like SPARQL-style content.
- Leave a Comment |
- Mark review as helpful
The future of databases is already here and it's a Graph database!
What do you like best about the product?
There are a lot of things that make a graph database awesome for every day usage. On of them is the fact that previous queries that would had to join a lot of tables are very easily to make now at huge speeds. Getting friends of friends that like something that you haven't is extremely easy to do and this makes it a perfect tool for Recommendations. And not any kind of recommendations but Real-Time Recommendations. It's the perfect tool for storing huge amounts of data that are very interconnected and getting data easily out using Cypher which is a perfect tool for anyone to understand, even non-technical people.
What do you dislike about the product?
I dislike only a couple of things. The fact that there's no possibility to store object data to nodes or relationships without flattening them before and the fact that there's no native data storage integrated.
What problems is the product solving and how is that benefiting you?
Recommendations. Neo4j enables us to do Real-Time Recommendations, from basic things like, if you liked this you might also like x,y,z to getting detailed social information like what friends of friends like and do to even more complex things like computing similarity between users, bulking them into buckets and recommending things that people in your bucket liked and you haven't seen yet.
One of the other cool things is that it's Whiteboard friendly, it's extremely easy to explain the structure and how things are connected in the database to non-technical users. Also, the query language (Cyphers) makes writing queries a breeze, and not only writing queries but also reading and understanding them by just taking a look at a query.
One of the other cool things is that it's Whiteboard friendly, it's extremely easy to explain the structure and how things are connected in the database to non-technical users. Also, the query language (Cyphers) makes writing queries a breeze, and not only writing queries but also reading and understanding them by just taking a look at a query.
Recommendations to others considering the product:
Definitely give it a try, especially if you have very interconnected data or a lot of social aspects (joining tables is not fun) also, if you know your app will change a lot, having the flexibility of starting with something simple and going to more complex data-sets is awesome. Finally, it's easy to understand (the concept of nodes and relationships is easy of anyone to grasp) so new programmers will be up and running in no time.
Graphs are everywhere - implement using Neo4j
What do you like best about the product?
Easy data modeling and installation and really awesome easy data import (Load CSV).
Good data visualization.
Good data visualization.
What do you dislike about the product?
Documentation - extensive example using Java in REST mode is big time missing - at-least I did not understand how to implement.
What problems is the product solving and how is that benefiting you?
Recommendation and Discovery, Tags and Categories.
Many to many relationship is resolved with ease.
Many to many relationship is resolved with ease.
NEO4J graphs database FTW
What do you like best about the product?
Great community, awesome in city meetups. The language is really simple compared to other data languages. Once you get into graphs, you need a framework that can express your thoughts easily. The neo4j graph language is fairly easy to understand and there are a LOT of toolkits available to map it to your environment. (graphs)-[:ARE]->(everywhere)
What do you dislike about the product?
I wish there was a vis tool to help learn the language. Although I said it's easy, I should have said it is the easiest. Without an instructor like at the city meetups, it is probably tough to learn it over a weekend. But WAY easier than other systems. At least you don't need to install java or some other crazy dependency. :)
What problems is the product solving and how is that benefiting you?
Graphs help define distances between relationships of entities. I was working on analysing cyber attacks to determine "strike" distance for a given attack against a given environment.
Recommendations to others considering the product:
Use neo4j, go to a city meetup.
LEARN graph concepts first. Do not try and stick RDBMS ideas and concepts or use cases into a graph.
graph is a special tool to apply node edge math. not a data store best suited for record keeping (USUALLY)
obviously your milage will very depending on your use case. But my advice to managers is to know if you have the right use case for this kind of database, e.g. distance - So if you can transform your data into a topology and your question can be phrased in a closeness / distance way, then you will be very successful.
LEARN graph concepts first. Do not try and stick RDBMS ideas and concepts or use cases into a graph.
graph is a special tool to apply node edge math. not a data store best suited for record keeping (USUALLY)
obviously your milage will very depending on your use case. But my advice to managers is to know if you have the right use case for this kind of database, e.g. distance - So if you can transform your data into a topology and your question can be phrased in a closeness / distance way, then you will be very successful.
A solid graph database
What do you like best about the product?
Neo4j provides an intuitive way to model real-world entities in a completely logical way.
What do you dislike about the product?
Given that it's still a fairly new database, community support is a little sparse.
What problems is the product solving and how is that benefiting you?
Modeling relationships between real world entities.
Recommendations to others considering the product:
Make sure you've got a way to control access to neo4j before deployment.
I use neo4j when I was an Intern at LinkedIn China.
What do you like best about the product?
It is a high efficiency graph database, the query language called 'cypher' is powerful. The visualization of the database (a web page) is beautiful.
What do you dislike about the product?
It is not distributed, so it will be slow when many queries come together. It has bugs, when I was an Intern at LInkedIn China, neo4j caused our service down.
What problems is the product solving and how is that benefiting you?
a social app backend service, we use neo4j to store users' information and relationships. due to the great query language 'cypher', we can query relationships between users on neo4j. If we use other no-graph database, those queries will be hard to resolve.
Recommendations to others considering the product:
great database to solve graph queries
Graph databases will open your eyes to possibilities you never knew before
What do you like best about the product?
Graph model. Powerful query language. Extensibility. Bindings for many languages.
I love their support for their community. They are great to work with, and answer their customers questions promptly. I've been in open source software for 17 years, and I think very highly of their community support.
The most important aspects of what we model are very well modeled by a graph database. We love the fact that you can ask questions like "What all depends on this system directly or indirectly". We can do the same for a network switch, and for a business process. It really rocks in this way. These are the questions you want to ask - and they're almost impossible to answer in a relational database.
I love their support for their community. They are great to work with, and answer their customers questions promptly. I've been in open source software for 17 years, and I think very highly of their community support.
The most important aspects of what we model are very well modeled by a graph database. We love the fact that you can ask questions like "What all depends on this system directly or indirectly". We can do the same for a network switch, and for a business process. It really rocks in this way. These are the questions you want to ask - and they're almost impossible to answer in a relational database.
What do you dislike about the product?
I need for some of my data to have more complex (map-like) attributes. I've worked around this, but it limits the queries I can perform in their database. I could write an extension that would take care of this, but I haven't. Having native maps would be a good thing. Instead I use JSON strings. It works for me.
What problems is the product solving and how is that benefiting you?
We create a model of your data center by discovery which then creates and keeps a Neo4j database updated. The most important thing about a data center is how all the pieces are connected logically and physically - how they talk to each other. This is where Neo4j shines.
Modeling IT infrastructure, software, networks, configuration, network connections, settings and lots more things. See http://AssimilationSystems.com for details.
In lots of ways, Neo4j is a perfect object store for our object-oriented software. Neo4j graph nodes just become objects in our code. It's a great match.
Modeling IT infrastructure, software, networks, configuration, network connections, settings and lots more things. See http://AssimilationSystems.com for details.
In lots of ways, Neo4j is a perfect object store for our object-oriented software. Neo4j graph nodes just become objects in our code. It's a great match.
Recommendations to others considering the product:
Get involved with their online community. They rock!
If you need blobs, that's something that's coming - but isn't there yet.
If you need blobs, that's something that's coming - but isn't there yet.
Easy to manage only by experts, yet powerful if you are one.
What do you like best about the product?
Certainly one of the best things of Neo4j is that it tackles social network data. This makes it easier to quickly load explore the network much more quickly than any other database, as others would requiring extracting the data first to some language like R and employ some social network analysis library such as igraph.
In our research group, Neo4J is also viable because it is open source. We would burn all our research funds in the database alone with other solutions.
They also released freely a book for Neo4j enthusiasts to learn how to make the best of it.
In our research group, Neo4J is also viable because it is open source. We would burn all our research funds in the database alone with other solutions.
They also released freely a book for Neo4j enthusiasts to learn how to make the best of it.
What do you dislike about the product?
The worst problem with neo4j is finding the right people to use it. Often times we want the database to be made public, and unfortunately not many people are versed in graph databases yet. For that case, even Neo4j being easy to use by an expert, it makes the data hard to access by the majority of database users.
What problems is the product solving and how is that benefiting you?
We are employing Neo4j for software engineering research, mainly for analyzing version control systems, mailing lists and bug trackers. As mentioned previously, the benefits were observed in manipulating the data entirely in the database rather than requiring a programming language on top of that.
Recommendations to others considering the product:
Make sure the community who could benefit from the data or research partners will be able to use the database.
Preparing for a large project
What do you like best about the product?
Really appreciate the speed and efficiency of the graph model. We're using it for a logistics platform and the ability to build relationships into the model from the start and quickly traverse relevant data is great. The interface for testing is really nicely designed and there's lots of appropriate help available.
What do you dislike about the product?
The biggest challenge is that so few people seem to be using it and there aren't that many resources. There are more and more all the time - there are lots of packages in various programming languages at different levels of development. The biggest challenge, though, is the lack of high-level strategy advice on best-practices with the architecture. Lots of just trying things out.
What problems is the product solving and how is that benefiting you?
We have a logistics platform that iterates on a lot of known values, so building those relationships into the model from point one is great. The query times are phenomenally fast. We hope that this will translate into lower hosting costs as the raw horsepower needed is much less.
Recommendations to others considering the product:
Spend plenty of time in their environment testing the model and making sure that the logic for nodes and relationships is solid. Once that's done you're stuck with it - the planning is a bit more important than with a SQL model. Since everything is RESTful based, the technical challenges aren't that large.
Developing complex, production applications on Neo4J
What do you like best about the product?
Neo4J is a true native graph database. As such it performs very, very efficiently for traversing even very large sets of connected data. It has proven to be highly robust, featuring true enterprise grade database features such as ACID transactions and automated backup and recovery.
Neo4J support has been absolutely outstanding as well. They are very responsive wether you are looking at a serious production outage (that may very likely even be your own fault) or something that just doesn't appear to do what you think it should do.
Neo4J support has been absolutely outstanding as well. They are very responsive wether you are looking at a serious production outage (that may very likely even be your own fault) or something that just doesn't appear to do what you think it should do.
What do you dislike about the product?
Sometimes the backup verification can take longer than I would like. I am also always looking forward to faster query resolution as the query planner continues to improve.
What problems is the product solving and how is that benefiting you?
We have enabling people to easily load released data that is locked into different files and then quickly query and analyze that data. Neo4J makes it possible for us to automatically link that data and query it in a fast and useable manner.
Recommendations to others considering the product:
Be aware that while there are other graph database products on the market, Neo4J is the creator of the properties based graph and is the only truly native graph database. It is not a graph layered on top of another database system.
showing 51 - 60