Neo4j vs. Graph Found (ONgDB) (2020)
casetext.com
casetext.com
They should have just forked it, changed the names which it looks like that's what they're doing going forward.
It's severely crippled, practically untunable and unmonitorable. You basically can't run it in a production context unless you're willing to take huge risks that it can shit the bed on you at any time and you're willing to rebuild from scratch.
I'm in a position where I have to do this and I'd like to flip Neo4j the finger every single day.
re: untenable: can you give us some more details? JVM tuning? Neo4J specific?
TBO, I use RDF datastores about 10x my use of Neo4J, but I appreciate their free edition. Another vendor who handles free vs. commercial well (in my opinion) is GraphDB, where the free edition is scalable to the largest single server you want to run it on, but only allows 2 simultaneous connections.
Some un-solicited advice: if you really need to scale a large graph database, look at BlazeGraph that supports both property graphs and RDF. It is fast, injests data very quickly, and just a few servers run all of WikiData. That codebase became Amazon Neptune, BTW.
I'm not saying it's not functional, because clearly it is, but it has no place in a corporate setting.
I'm actually well aware of (much better) alternatives, but this tool was chosen by people in the org who gave no consideration to licensing, or requirements to run in production and are senior enough that there's no one to go around them to fix the situation.
https://www.graphfoundation.org/blog/graph-foundation-resolu...
Don't bathrooms have vending machines that say "Compare with Boss by Hugo".