Graph Data Modeling Fundamentals

Who this course is for

This course is for developers and data engineers who need to design the graph behind a Neo4j application. If you have learned CypheriFull definition for Cypher (opens in a new tab)Neo4j's implementation of GQL, the ISO standard query language for graph databases. It is declarative: you describe the pattern to find, and the database decides how to find it. and can read and write data, but you are unsure how to decide what should be a nodeiFull definition for node (opens in a new tab)A vertex in a graph. In a property graph it can carry labels and properties., what should be a relationshipiFull 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., and what should be a propertyiFull definition for property (opens in a new tab)A named value stored on a node or a relationship., this course gives you a repeatable method. No prior modeling experience is assumed, but you should complete Neo4j Fundamentals and Cypher Fundamentals first, since you will use MATCH, MERGE, and CREATE throughout to create nodes, add relationships, and refactor the graph.

What you'll do

This is a hands-on course. You will model and build a real Movies graph, starting from the use cases the application must support and turning them into a working model. You will create Movie and Person nodesiFull definition for node (opens in a new tab)A vertex in a graph. In a property graph it can carry labels and properties., connect them, and then repeatedly test the model by asking whether it can answer the use-case questions — the discipline that keeps a graph model honest. You will use an instance modeliFull definition for instance model (opens in a new tab)A data model drawn with real example data, showing particular nodes and relationships rather than their types., real sample data, to confirm your queries return what you expect.

When testing reveals a weakness, you refactor. You will add Actor and Director labelsiFull definition for label (opens in a new tab)A tag on a node that groups it with other nodes of the same kind. A node can carry more than one. and retest to confirm your queries still work and now run faster. You will eliminate duplicated data by promoting repeated propertyiFull definition for property (opens in a new tab)A named value stored on a node or a relationship. values, such as a movie's language and genre, into their own Language and Genre nodes so each fact is stored once. You will replace generic relationshipsiFull 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. with specific types such as ACTED_IN, DIRECTED, and RATED, so a query can follow exactly the relationships it needs and skip the rest. And you will introduce intermediate nodes, for example a Role node that captures the character a person played in a specific movie, to model facts that connect more than two entities. By the end you will have a model that is both correct and fast for its intended queries, and a process you can reuse on your own domain.

Where to go next

Once you can design a model, you need to load data into it. Importing Data Fundamentals teaches you how to import data from CSV files into a Neo4j graph, applying the modeling decisions you made here. Data modeling is also a core topic on the Neo4j Certified Professional certification exam, so the skills you build in this course move you directly toward that credential.