Having the option for combined graph and document store was just what we needed. We were replacing a Mysql implementation of our product. Replacing the iterative collection of data with a graph traversal improved performance 1000x. The document store...
No ANSI SQL support, I was hopping for SQL support, that was a disappointing thing to learn a new language. We use CQL at the moment, Spark SQL, and SQL on MySQL, now we have to adapt to AQL which is an unnecessary overhead in my opinion.
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...
Initial learning curve. poor documentation. integration with C# environment. Documentation for neo4jclient for c# is pathetic.
Having the option for combined graph and document store was just what we needed. We were replacing a Mysql implementation of our product. Replacing the iterative collection of data with a graph traversal improved performance 1000x. The document store...
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...
No ANSI SQL support, I was hopping for SQL support, that was a disappointing thing to learn a new language. We use CQL at the moment, Spark SQL, and SQL on MySQL, now we have to adapt to AQL which is an unnecessary overhead in my opinion.
Initial learning curve. poor documentation. integration with C# environment. Documentation for neo4jclient for c# is pathetic.