I am studying using a graph database (e.g. neo4j - mainly because I need python bindings) to simulate a real physical network. however, one of the requirements is to keep track of the history of where the machines were, the status of network ports, etc.
now, in a relational database, I can easily create an archive table that I can use to perform historical queries; however, I have been bitten many times by problems with fixed table schemas and rather uncomfortable left joins everywhere.
Are there any suggestions on how it would be better to maintain historical relationships and node properties in the graph database?
source
share