Neo4j is a leading graph-based database optimized for storing and managing data relationships. It enables flexible data modeling and supports complex queries in real-time.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Technical building block: can be automated, integrated, or operated.
Concrete cog in the system that works inside larger relationships.
Neo4j is a graph database that stores entities as nodes, their relationships as edges, and queries them with Cypher.
Emil Eifrem, Johan Svensson, and Peter Neubauer started Neo4j in 2000 to model highly connected domain data more naturally and efficiently than tables allowed.
Imagine a map: places are nodes, roads are relationships, and a query follows the paths relevant to its question.
A node represents an entity with properties.
A directed or typed edge connects two nodes semantically.
Cypher is the declarative query language for graph patterns.
Neo4j fits domains where relationships are first-class information, such as dependencies, recommendations, and knowledge graphs.
Where this building block is located in the topic model.
No structure path available.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.