Live data from Hacker News

Apache AGE, a PostgreSQL extension with graph database functionality

github.com

21–30 of 77 posts

Re: Apache AGE, a PostgreSQL extension with graph database functionality

#21

Could it be efficient to use Apache AGE for e.g. retrieving all comments on an article? Currently I’m using materialized paths to efficiency return all commments but would be keen to know if AGE can help query comments for an article more powerfully.

The ltree extension (https://www.postgresql.org/docs/current/ltree.html) is perfect for this usecase.

Re: Apache AGE, a PostgreSQL extension with graph database functionality

#23
post #5

Anyone tried this? How does the performance compare to neo4j and RedisGraph? I’m about to give RedisGraph a try and I guess I will try this one a go as well.

Did you try dgraph? For our use cases it won over neo4j. Didn’t try redisgraph.

Re: Apache AGE, a PostgreSQL extension with graph database functionality

#25
post #5

Anyone tried this? How does the performance compare to neo4j and RedisGraph? I’m about to give RedisGraph a try and I guess I will try this one a go as well.

Did you try dgraph? For our use cases it won over neo4j. Didn’t try redisgraph.

We benchmarked all 3; redisgraph was fastest by far.

Re: Apache AGE, a PostgreSQL extension with graph database functionality

#26
post #5

Anyone tried this? How does the performance compare to neo4j and RedisGraph? I’m about to give RedisGraph a try and I guess I will try this one a go as well.

Did you try dgraph? For our use cases it won over neo4j. Didn’t try redisgraph.

Didn't dgrapgh dissolve? Based on open functionality discussed on their help forum and stbility issues I wouldn't touch it any more.

A product which lived up for VC money and little more.

Re: Apache AGE, a PostgreSQL extension with graph database functionality

#27
post #3
post #2

What subset of the openCypher dialect specification will Apache Age support? Every implementation is all over the place and completely non-portable. And neo4j performance leaves much to be desired. My personal go-to is RedisGraph paired with RedisInsight for the instant visualizations. It just feels "right" and, while not perfect, is overall intuitive.

I've been following RedisGraph with great interest since I first heard about it. Fell in love with cypher but not a big fan of neo4j. Most recently I've been playing with EdgeDB (not cypher-based) which scratches my graphDB itch pretty well but it's still a little too early for me to consider adopting it in a serious project. I'm glad there seems to be continued interest in graphDBs, I think there's a lot of potentia…

We might see a clear winner in query language, not product. What is the clear winner in relational databases? SQL certainly but what product?

Re: Apache AGE, a PostgreSQL extension with graph database functionality

#28

Earlier quoted context omitted.

Did you try dgraph? For our use cases it won over neo4j. Didn’t try redisgraph.

Didn't dgrapgh dissolve? Based on open functionality discussed on their help forum and stbility issues I wouldn't touch it any more. A product which lived up for VC money and little more.

No.

Re: Apache AGE, a PostgreSQL extension with graph database functionality

#29
has anyone here worked on graph neural networks ? basically creating embeddings for node based on their edge connectivity (or reachability) and using that for neural networks ?

how do you do this at scale ?its generally a NP hard problem, but wondering whether something like AGE helps.

not sure how Google, etc or even someone on fraud detection does this at scale

Re: Apache AGE, a PostgreSQL extension with graph database functionality

#30
This is written in C. I wonder how common it is to write PG extensions in safer langugaes and what would be the most suitable.

I'm somewhat wary of using nontrivial C extensions, having seen so many of them sometimes seg fault the backend (eg PostGIS). There seem to be PG backend crashes described in this projects issues as well.

Post reply on HN