Neo4j

14 engineers on Hacker News describe using Neo4j first-hand: 4 endorse it, 5 regret it, 1 are mixed.

46%trust
14first-hand users
14in production
endorse 4mixed 1regret 5uses, no opinion

“In the end we switched to using Neo4j and were able to build new features a lot more quickly”

endorse · production · henryfjordan · 2023-03-31 · source ↗ · wrong label?

“we reached the limit of 32 billions of unique IDs (Neo 3.2 if I remember well). And had to wait for the next version so we could add more data.”

regret · production · lolive · 2022-12-09 · source ↗ · wrong label?

“Once we switched to neo4j, the same query was a single, easily readable line.”

endorse · production · 2 yr · mcv · 2021-07-10 · source ↗ · wrong label?

“At my company we used Neo4J, that sucked and it was too expensive.”

regret · production · iaabtpbtpnn · 2021-02-05 · source ↗ · wrong label?

“Neo4J is used in production at my company. We have had problems with the clustering architecture known as HA.”

mixed · production · lolive · 2018-11-01 · source ↗ · wrong label?

“I've used it in production settings where it was NOT crushing a use case.”

regret · production · mschaef · 2018-11-01 · source ↗ · wrong label?

“I've been using Neo in production on GrapheneDB with py2neo and Flask for about a year. Love it.”

endorse · production · 1 yr · motohagiography · 2018-11-01 · source ↗ · wrong label?

“it didn't scale for our use case (primarily because of its master-slave architecture and other bugs and limitations here and there).”

regret · production · javadev80 · 2017-07-05 · source ↗ · wrong label?

“it's been a great fit at the two startups I used it at since I got to implement it from the ground up”

endorse · production · mcphilip · 2015-06-11 · source ↗ · wrong label?

“In the end we switched to postgres because the cognitive load was lower, the tooling was better”

regret · production · aidos · 2014-01-08 · source ↗ · wrong label?

“we run everything local (ollama + neo4j) for compliance reasons”

neutral · production · kaziava · 2026-09-16 · source ↗ · wrong label?

“For one Graphistry project, we run a single node neo4j with 0.5b nodes/edges, so something in the description isn't adding up”

neutral · production · lmeyerov · 2021-08-11 · source ↗ · wrong label?

“we run a HA Neo4j DB deployment as a Marathon service pegged to a handful of nodes”

neutral · production · estill01 · 2017-09-06 · source ↗ · wrong label?

“An old job used Neo4j, and the graph concept was great for specific use cases.”

neutral · production · badtuple · 2017-04-08 · source ↗ · wrong label?