<story><title>Neo4j nabs $80M Series E as graph database tech flourishes</title><url>https://techcrunch.com/2018/11/01/neo4j-nabs-80m-series-e-as-graph-database-tech-matures/</url></story><parent_chain><item><author>hardwaresofton</author><text>Neo4J has been around so long -- is anyone here using it in production and really happy with it, where it&amp;#x27;s like &lt;i&gt;really&lt;/i&gt; crushing a use-case?&lt;p&gt;I feel like 90% of the applications in existence can go so far with a regular RDBMS that they never try out Neo4j... I know that&amp;#x27;s the case with me. Half the time I think I&amp;#x27;d just try throwing Agensgraph[0] at the problem instead of jumping to the community version of Neo4J.&lt;p&gt;[0]: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;bitnine-oss&amp;#x2F;agensgraph&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;bitnine-oss&amp;#x2F;agensgraph&lt;/a&gt;</text></item></parent_chain><comment><author>ThePhysicist</author><text>In general I think that graphs are a very good fit for many problems in analytics (e.g. fraud detection, logistics) and having a database that treats graphs as first-class citizens is a good thing as well.&lt;p&gt;I&amp;#x27;ve used Neo4j in the past and it seemed to be stable and efficient, not sure about how well it scales though.&lt;p&gt;Before, TitanDB (now JanusDB) in conjunction with the Tinkerpop stack was probably my favorite graph DB&amp;#x2F;stack, but not sure how seriously Datastacks (who owns TitanDB now) continues developing it. And JanusDB as a project didn&amp;#x27;t seem very active to me (I could be wrong of course).&lt;p&gt;That said, you can construct and handle graphs using relational databases, graph databases give you advantages in that they have (often) better indexing (i.e. O(1) lookups of vertices &amp;amp; adjacent edges) and come with graph querying languages (e.g. Gremlin), which make it much easier to work with graphs compared to SQL (you can use recursive CTEs to walk graphs on the database side as opposed the client side but complex queries are hard&amp;#x2F;impossible to write like that). I&amp;#x27;ve written a graph DB abstraction layer in the past that also supports SQL backends: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;7scientists&amp;#x2F;vortex&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;7scientists&amp;#x2F;vortex&lt;/a&gt;.</text></comment>
<story><title>Neo4j nabs $80M Series E as graph database tech flourishes</title><url>https://techcrunch.com/2018/11/01/neo4j-nabs-80m-series-e-as-graph-database-tech-matures/</url></story><parent_chain><item><author>hardwaresofton</author><text>Neo4J has been around so long -- is anyone here using it in production and really happy with it, where it&amp;#x27;s like &lt;i&gt;really&lt;/i&gt; crushing a use-case?&lt;p&gt;I feel like 90% of the applications in existence can go so far with a regular RDBMS that they never try out Neo4j... I know that&amp;#x27;s the case with me. Half the time I think I&amp;#x27;d just try throwing Agensgraph[0] at the problem instead of jumping to the community version of Neo4J.&lt;p&gt;[0]: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;bitnine-oss&amp;#x2F;agensgraph&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;bitnine-oss&amp;#x2F;agensgraph&lt;/a&gt;</text></item></parent_chain><comment><author>gibsonf1</author><text>There are two kinds of graph databases, property graph and rdf semantic graph.  Neo 4J is the former, which I don&amp;#x27;t think is that useful in primarily only showing some kind of relation between things.  The rdf semantic graph approach, however, captures the semantics of the relationship allowing inference and queries not normally possible with rdbms.&lt;p&gt;It&amp;#x27;s an easier cultural change in thinking from rdbms to property graph, but also not a huge improvement in terms of what you can do vs an rdbms.  Going with a full semantic graph where the relationship is also represented by a node with unlimited relationships, and moving and thinking in hierarchies and inference, is a complete cultural change with an impressive productivity and capability improvement not possible with rdbms.  Allegrograph is a good example of a semantic graph which can handle trillions of triples.</text></comment>