In this lesson, you will learn how to transition from a static snapshot of a graph to a dynamic structure that tracks how relationships evolve over time.
Moving Beyond Static Snapshots
In standard property graphs, an edge between two nodes is typically binary: it either exists or it does not. However, in many real-world scenarios—such as a user's employment history or a social media connection—a relationship is not permanent. It begins, persists, and potentially ends. To track this, we move from a "snapshot" model to a "time-aware" model by augmenting our edges with temporal metadata.
The Temporal Property Approach
The most common way to implement this is to treat the "Time" element as a first-class property of the relationship itself. Instead of a single edge representing a connection, we store a history of state transitions on that relationship.
Imagine a relationship between an Employee and a Company. Instead of a simple WORKS_AT edge, we include start_date and end_date properties.
-- Conceptual representation of a time-aware edge
MATCH (e:Employee {name: 'Alice'})-[r:WORKS_AT]->(c:Company {name: 'TechCorp'})
WHERE r.start_date <= '2023-01-01'
AND (r.end_date IS NULL OR r.end_date >= '2023-01-01')
RETURN e, r, c
Challenges of Temporal Graphs
While adding start_date and end_date properties is straightforward, query complexity increases significantly. When you perform path traversal, the engine can no longer simply hop from node to node. It must validate that the relationship was active at the specific "point-in-time" you are interested in.
If you need to represent complex changes—such as a relationship changing its weight, type, or attributes over multiple intervals—you might move to an Interval-based Model. In this design, a single logical relationship is represented by a sequence of discrete edge versions, each valid for a specific time window. This allows you to perform "time-travel" queries to see exactly how the graph looked at any historical moment, though it requires careful indexing on your temporal properties to keep traversal performance high.
Key Takeaway: Time-aware graphs extend the property model by treating the existence of a relationship as a temporal interval, requiring traversal logic that accounts for the validity period of each edge.