<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></parent_chain><comment><author>motohagiography</author><text>I&amp;#x27;ve been using Neo in production on GrapheneDB with py2neo and Flask for about a year. Love it.&lt;p&gt;The reason I use a graph is for consistency from my product level business logic to my implementation.&lt;p&gt;Basically, to solve my problem, I started with a set of english statements, which yielded a grammar, that I described as &amp;quot;objects and morphisms,&amp;quot; (things and relationships) then implemented it in a graph - put a front end on it and built a product.&lt;p&gt;Graphs provide coherence to my problem. Could an RDBMS do this? Yes, but not without a complex intermediate query layer. I think of using a graph as analogous to specifying your problem in terms of a functional language instead of imperatively. The reason to do that is because your product is the result of  maintaining consistency of an  abstraction, like a DSL or a game, instead of just retrieving stored values, documents and their variations.&lt;p&gt;It&amp;#x27;s disruptive to a lot of orgs as well, since there is a lot of sunk cost in RDBMS experience, so I think the applications are all net new projects. I don&amp;#x27;t foresee anyone migrating to one, but I do see a point where majority of new products use one.</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></parent_chain><comment><author>drej</author><text>I had a toy project which housed all its data in Postgres and I needed a bit of graph traversal, really basic stuff. I almost prepared some ETL to load the data into neo4j&amp;#x2F;redisgraph, but then I found out about recursive CTEs in Postgres.&lt;p&gt;Granted, they won&amp;#x27;t let you do nearly as much as some advanced graph algorithms, but the ease with which you can use it in your operational data store is amazing. And with proper indexing, I could do a traversal in hundreds of milliseconds.&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;www.postgresql.org&amp;#x2F;docs&amp;#x2F;current&amp;#x2F;static&amp;#x2F;queries-with.html&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.postgresql.org&amp;#x2F;docs&amp;#x2F;current&amp;#x2F;static&amp;#x2F;queries-with....&lt;/a&gt;</text></comment>