I wrote a driver for MongoDB in 2010, but then moved onto Neo4j in late 2013. I liked Neo4j quite a bit, it could handle all the sensor/IoT data we could throw at it. Back then it had (and I'm sure still does) a beautiful interactive data visualization dashboard, great Cypher tutorials, and more. Neo4j is a good database. I went to write a database driver for it, and found it extraordinarily difficult. I knew it woul…
What’s gun, you mean gnu open source ?
Ask HN: If you've used a graph database, would you use it again?
11–20 of 84 posts
Re: Ask HN: If you've used a graph database, would you use it again?
#12Re: Ask HN: If you've used a graph database, would you use it again?
#13I started using Neo4j 8 years ago after a long time as a relational database developer. I needed it for a project building a LinkedIn clone with skills (at the time LinkedIn didn't have skills). I was going to need a massive join table of user-skill-user and decided it was best in a graph. I built a ruby gem "neography" as a Neo4j driver and became an open source contributor. Later Neo4j contracted me to build a rule…
Re: Ask HN: If you've used a graph database, would you use it again?
#14Earlier quoted context omitted.
What’s gun, you mean gnu open source ?
Likely they're referring to https://github.com/amark/gun , which they refer to earlier. amark is Mark Nadal.
Hey, I noticed your nice resources in your profile - particularly Haidt. For my wife's PhD, she worked with Baumeister, a colleague of Haidt. Would love to hear more about your interest in civil discourse and other such things! Shoot me an email?
Re: Ask HN: If you've used a graph database, would you use it again?
#15Earlier quoted context omitted.
Likely they're referring to https://github.com/amark/gun , which they refer to earlier. amark is Mark Nadal.
Thanks, yes (you and xumingmingv) are correct. Hey, I noticed your nice resources in your profile - particularly Haidt. For my wife's PhD, she worked with Baumeister, a colleague of Haidt. Would love to hear more about your interest in civil discourse and other such things! Shoot me an email?
Re: Ask HN: If you've used a graph database, would you use it again?
#16Interesting question. I think it is critical to point out that, the underlying principles for a graph database is different from RDBMS, because the operators in a graph database may not comply to relational algebra. Consider the following case: Client A issues a query -- starting from a vertex, conduct bounded closure search, giving every visited vertex a mark (coloring, or lexical flag, whatever you would expect fro…
Re: Ask HN: If you've used a graph database, would you use it again?
#17The advantages are that it's just sql, has good performance, and we can query the graph using relational logic rather than n+1 traversal. The trade off is space (the closure table has the potential to be huge).
So it depends on the size of the data set. Part of me wishes we'd built something that's easier to partition, but for now that's a future concern.
Re: Ask HN: If you've used a graph database, would you use it again?
#18Interesting question. I think it is critical to point out that, the underlying principles for a graph database is different from RDBMS, because the operators in a graph database may not comply to relational algebra. Consider the following case: Client A issues a query -- starting from a vertex, conduct bounded closure search, giving every visited vertex a mark (coloring, or lexical flag, whatever you would expect fro…
"Claiming ACID" what is ambiguous about that? Transaction support with different serialization levels, like other databases that offer it.
And Neo4j originally started b/c RDBMS was not able to execute the complex deep traversals needed in real time. Dedicated storage & query engine for graphs allow you to run statements quickly that would otherwise take too long to execute.
Regarding the data model, the property-graph model is much closer to the object model but with richer relationships, it doesn't suffer from the object-rdbms impedance mismatch and is better suited to express real-world domains & scenarios. It also represents semantic relevant relationships as first class citizens in the database, allowing for proper information representation and much faster retrieval.
Disclaimer: I work with/for Neo4j, for 8+ years and still love it.
Re: Ask HN: If you've used a graph database, would you use it again?
#19I wrote a driver for MongoDB in 2010, but then moved onto Neo4j in late 2013. I liked Neo4j quite a bit, it could handle all the sensor/IoT data we could throw at it. Back then it had (and I'm sure still does) a beautiful interactive data visualization dashboard, great Cypher tutorials, and more. Neo4j is a good database. I went to write a database driver for it, and found it extraordinarily difficult. I knew it woul…
Re: Ask HN: If you've used a graph database, would you use it again?
#20Interesting question. I think it is critical to point out that, the underlying principles for a graph database is different from RDBMS, because the operators in a graph database may not comply to relational algebra. Consider the following case: Client A issues a query -- starting from a vertex, conduct bounded closure search, giving every visited vertex a mark (coloring, or lexical flag, whatever you would expect fro…
I think that in a graph database, the ACID property comes at a greater cost, but to me it's a tool I use as a secondary store, derived from the "truth" in the RDBMS. I use it to store the data more efficiently for queries and to query data in a discovering fashion that would significantly more complicated in the underlying RDBMS.