[metadat]

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.

[bavell]

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 potential in that space and I'm eagerly awaiting a clear winner to emerge.

[jhoechtl]

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

[flymetothemoon]

The Apache AGE is inspired by AgensGraph, a multimodel database fork of PostgreSQL. So it uses AgensGraph dialect.

[bayesian_horse]

AGE is an extension, not a fork. You can have relational tables and graphs in the same database, probably you can also use both in the same query.

[flymetothemoon]

That's right, AGE is designed to use both queries either separately or together. SQL (PostgreSQL), openCypher (AGE)