31–40 of 56 posts
Earlier quoted context omitted.
If you want a production-grade graph DBMS, you don't have that many OSS options that are reliable and well-supported. In the relational space, it took OSS options like Postgres many decades (and somehow paid-for person-years) to get to a place where enterprises seriously consider migrating off Oracle to it.
Are there any? My experience so far with graph databases is a resounding failure.
But doesn't actually show the thing.
That's AI hypecycle signal for probably bullshit/defective thing.
I think I found a place Dodge can save some money. Memgraph pricing is ridiculous.
Even paying a college grad to babysit a server costs more than their yearly rate. I assume you're speaking as someone who loves to host everything for themselves, but the logic is surely different in enterprise/government, no?
Earlier quoted context omitted.
If you want a production-grade graph DBMS, you don't have that many OSS options that are reliable and well-supported. In the relational space, it took OSS options like Postgres many decades (and somehow paid-for person-years) to get to a place where enterprises seriously consider migrating off Oracle to it.
Are there any? My experience so far with graph databases is a resounding failure.
> "To make sure everyone understands that, I prefer label property graphs over RDF." I have two major issues with virtually all graph DBMSs that are not RDF/SPARQL-based: 1) They do not allow structure-preserving querying. That is, I query a graph and want the results to be a smaller graph. This is trivial in SQL, you just 'SELECT * FROM x WHERE ...' and the result set you get is tabular just like the table x. In SPA…
I'm not sure what you mean by this. The result of a query in neo4j is a set of nodes with specified relations linking them. It is much more flexible than the way SQL can only return a single table.
As an alternative to a pure graph db (e.g. here, memgraph), has anyone here used Apache's AGE graph-database extension for Postgresql? For making a knowledge graph that can live alongside SQL?
I believe AGE has unfortunately been defunded: https://github.com/apache/age/discussions/2150 It’s a shame because it seemed like being able to query data across multiple paradigms would be really useful
See https://www.w3.org/2001/sw/sweo/public/UseCases/Nasa/ for a public case study.
This work led to Stardog.
Which is used extensively in NASA today—
https://gpdisonline.com/wp-content/uploads/2019/09/StardogNA...
https://www.informationweek.com/machine-learning-ai/stardog-...
> "To make sure everyone understands that, I prefer label property graphs over RDF." I have two major issues with virtually all graph DBMSs that are not RDF/SPARQL-based: 1) They do not allow structure-preserving querying. That is, I query a graph and want the results to be a smaller graph. This is trivial in SQL, you just 'SELECT * FROM x WHERE ...' and the result set you get is tabular just like the table x. In SPA…
"They do not allow structure-preserving querying. That is, I query a graph and want the results to be a smaller graph." I'm not sure what you mean by this. The result of a query in neo4j is a set of nodes with specified relations linking them. It is much more flexible than the way SQL can only return a single table.