ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Databases & messaging · #neo4j
A decision guide for choosing between Neo4j GDS Louvain and custom Cypher for community detection, covering performance trade-offs, memory constraints, and implementation.
Learn how to match Neo4j index types to query patterns and integrity needs, avoid unnecessary scans, and validate choices with PROFILE and constraint tests.
Learn how Neo4j’s native full‑text indexes can cut query latency from seconds to milliseconds, what trade‑offs to watch for, and a step‑by‑step example that shows how to create, query, and monitor a full‑text index in a graph of millions of nodes.
Cypher's variable-length path patterns answer 'what's connected within N hops' in one line — but the hop bound and relationship-type filter are what stand between a fast query and a full-graph scan.
Deploy a single Neo4j 5.x instance with Graph Data Science for fast community detection on millions of nodes. This guide covers requirements, minimal design, trust boundaries, operational checks, failure modes, and scaling triggers.
Role-Based Access Control in Neo4j Neo4j 4.x and 5.x expose predefined roles such as read, write, and admin, and allow custom roles to be defined. The goal is to apply least‑privilege authentication while ensuring that users cannot continue to authenticate with a password that has surpassed an acceptable age. Current Constraints Passwords are stored internal
Goal: Clarify whether Neo4j’s storage layer should automatically retry obtaining an exclusive lock on its data directory when a transient NFS latency causes the initial lock attempt to fail, or whether it should treat the failure as fatal and shut down immediately. Constraints: The behavior varies between Neo4j 3.x, 4.x, and 5.x releases and can be influence
Neo4j manages transaction lifecycles through dbms.transaction.timeout configurations and driver-level settings. While the system is designed to terminate long-running operations, there is uncertainty regarding how the engine handles resource cleanup when a client abruptly closes a session versus a natural timeout expiration. When a client-side session is clo