[WirelessGigabit]

Part of our team uses Neo4j. It's a giant pain in the ass. The amount of time we've spent on the phone with their support trying to unravel bugs that they caused is insane. We don't get that with a paid product like MSSQL. Hell, Postgres isn't that bad and it's FREE!

The cost of Neo4j also went up with their new model. (see https://neo4j.com/blog/open-core-licensing-model-neo4j-enter...)

And they did the thing with the closing their source which nasty.

Then there's the separation of OnGDB which we looked at, but that didn't go well either. One day they deleted all of their packages. All gone. Thank God we had caches, but it took them a while to come back online. In hindsight because Neo4j had sued them. I understand that but that caused a LOT of headaches.

I feel that Graph databases are one of those things like Document databases. You probably don't need it...

[qorrect]

> I feel that Graph databases are one of those things like Document databases. You probably don't need it...

I got a really good chuckle out of that.

[zeninma]

I am curious for your insights on why Neo4j is still used despite all the pains it incurred? What would be a better approach to solve the same problem with a more conventional DBMS like Postgres? Thanks!