JanusGraph – Distributed, open source, scalable graph database • Hacker News Board

Re: JanusGraph – Distributed, open source, scalable graph database

#41

Post by fulafel » Thu, Jul 08, 2021, 5:54 AM UTC

mrdoops wrote: post #15

A lot of comments not sure about what Graph DBs are good for: * Flexible knowledge association i.e. Knowledge Graphing * Modeling and querying associations / models with many-steps-removed requirements * Expert Systems / Inference Engines * Lazy traversal for complex job scheduling Graph DBs are not good at being a general purpose 95% of use cases database. Just use Postgres/MySQL if you're not sure. We use Neptune (…

There are many other applications that work well with graph / triple store style approach to data. See eg Datomic and the several Datomic inspired databases (like Crux, Datahike, Datalevin, etc) used as general work horses in the Clojure world.

I'd recommend trying non relational databases even if you're not sure.

Re: JanusGraph – Distributed, open source, scalable graph database

#42

Post by AtNightWeCode » Thu, Jul 08, 2021, 6:35 AM UTC

staticassertion wrote: post #30

AtNightWeCode wrote: post #20

Earlier quoted context omitted.

I am a senior IT architect. I give you the junior card but in the whole, you don't know at all what you are babbling about. ALL databases have tradeoffs.

This is practically parody... I'm the founder of a company building a graph product. I've talked to numerous researchers in the field, read papers on the subject, I've even reviewed PHD candidates thesis for universities. I routinely field offers for consulting explicitly on graph database technology. You haven't said anything of substance and the little you have said has only served to convey your own ignorance on t…

I worked with graph databases. I also worked with graph like queries in SQL databases a lot for investigating money laundering, flow of payments between users and so on. In single systems that handles billions of Euros. This is easily done in SQL databases and has been since the eighties.

In general the only reason to use a graph database as I wrote is when you want to trade expensive writes for cheap ad hoc graph queries. So if you are investigating international money laundering with a lot of different types of relationships between different types of entities and it is significant how the entities are related then SQL can be a poor fit. Or at least, you probably need to model a lot of the relationships as entities and keep on evolving the model with new data. With graph databases you could just enter all the data from different sources as nodes and edges and then perform any query on that data still with good performance. At least in theory. In practice it can be difficult to model graph databases too.

The parody is that people suddenly thinks that there is a general need for graph databases.

Re: JanusGraph – Distributed, open source, scalable graph database

#43

Post by antpls » Sat, Jul 10, 2021, 11:44 AM UTC

To me, the downside of graph db is the non-standardized query language.

I tried Gremlin but it feels like an imperative DSL. Cypher queries are more readable, but are limited to Neo4J. I am looking forward for Open Cypher or maybe a variation of Facebook GraphQL.