While it's true that it is possible to create queries that only a graph database can answer, the performance of graph database on any given query varies wildly and can give you some pretty surprising results. I would look to store it on some other server (like S3) and save the url to that file in Neo4j/Arango. I don't know that storing picture or video data is a great idea in either ArangoDB or Neo4j. I believe that Neo4j solves a similarly narrow problem, as evidenced by how common it is to use Neo4j alongside some other data store. The only thing it’s good at is storing arbitrary pieces of JSON. MongoDB’s ideal use case is even narrower than our television data.
Arangodb vs neo4j tv#
Sarah Mei wrote an epic blog post about MongoDB, using an example with some data about TV shows. One thing that might help your decision making process is recognizing that many NoSQL databases solve a much narrower problem than people appreciate.
Both can be used from Java (though Neo4j can be embedded).
Arangodb vs neo4j code#
Any recommendations on which database management system is better suited? I will be writing the code in Java (and some Scala).īoth ArangoDB and Neo4j are capable of doing the job you have in mind.īoth projects have amazing documentation and getting answers for either of them is easy. What I got is that Neo4j better supports an manufacture independent query language, but I guess it is easier and better to learn the manufacturer standard. Also posts and such should be stored in the database. I do not want a different database, so it would be nice to store an image (byte array) in the database, maybe even different sizes for each image / video whatever. I would like to have an user node an to each person 2 eg.Īnd there is a need that there is an index on the edges. They can be json, but I do not care if the DB understands JSON.ĪrangoDB can also store documents and Neo4J is "only" a graph Database. I would like to store attributes on the edges and on the nodes. Persons have other persons as friends) and I guess a graph database would do the trick better than a classic database.
0 kommentar(er)
