Enforcing Data Models
You have designed a iFull definition for data model (opens in a new tab)The labels, relationship types and properties chosen to represent a domain. and tested it against your use cases. But testing only proves the model works when the right data is in the graph. What prevents the wrong data from getting in?
Without enforcement, any application or user with write access can create iFull definition for node (opens in a new tab)A vertex in a graph. In a property graph it can carry labels and properties. and iFull definition for relationship (opens in a new tab)A named, directed connection between two nodes. Every relationship has a type, a start node and an end node. that violate your model:
Join GraphAcademy to keep learning
Create your account to unlock 80+ hours of hands-on Neo4j courses, track your progress, and earn a certificate when you complete the course.
Sign in or register