Re:Representing Graphs in PostgreSQL
by manojlds on Monday February 17, 2025 @07:59AM
(#43078506)
Yeah Cypher was so good and made everything so intuitive. Loved working with Neo4J for a prototype and then had to face the licensing issues and huge costs and had to abandon it.
[ Parent
| on HN ]
I got bitten by the same, we were looking at switching to memgraph (which is also Cypher, but C++ rather than Java), sadly abandoned for other reasons ...
Re:Representing Graphs in PostgreSQL
by CharlieDigital on Monday February 17, 2025 @08:24AM
(#43078744)
What reasons? Would love to know for future ref.
If your org is amenable to Google Spanner or already using Spanner, it has preview support for Cypher and graph semantics: https://cloud.google.com/spanner/docs/graph/overview
Unrelated to the tech, just the graph-based algorithm (recommender stuff) that we had in mind did not give us the results we were hoping for ... and other things were queued up to be tried ...
Re:Representing Graphs in PostgreSQL
by mark_l_watson on Monday February 17, 2025 @09:20AM
(#43079254)
There are open source alternatives to Neo4J, and also very good scalable open source graph databases with query languages similar to Cypher. I think we are in agreement that it is a good idea to choose platform that scales both for compute and all other costs, like licensing costs.
Re:Representing Graphs in PostgreSQL
by CharlieDigital on Monday February 17, 2025 @09:23AM
(#43079285)
Can you list them?
Not sure if you everyone reading is aware, but Neo4j did end up turning Cypher into the openCypher spec and that allowed a lot of other graph stores to adopt Cypher as a query language.