I should probably put in some estimates of the sort of orders of magnitude of data involved: Books are in the 100s Effects are in the 10,000s / day Elements are in the 100s / Book
On Tue, Jun 14, 2011 at 8:07 PM, Patrik Sundberg <[email protected]>wrote: > Hi, > > Design question: > I have a Book. A book has Elements. To change what Elements are in a Book > there are Effects. An Effect adds or deletes an element from a Book (and has > other info). Everyday I archive the state of a Book so that I can easily get > the state of the Book (it's Elements) at a historical point in time. The > number of elements and which elements are in a Book vary from day to day > depending on the Effects taking place in the time period. > > So it's a bit like "Book contents archive of day X + 1 = Book contents > archive of day X + the Effects between X and X + 1" > > There's no need to represent the daily archives in any way, it's the > functionality of having historical snapshots that matter to me, so that one > can easily get the state of a Book at any point in time by finding the > closest archive point before the time and applying the Effects from that > archive timestamp and the point of interest. > > Ideally want to keep a long time history of Book state and Effects. > > Any ideas for an effecient of organizing this in a graph friendly way? > > Thanks, > Patrik > > _______________________________________________ Neo4j mailing list [email protected] https://lists.neo4j.org/mailman/listinfo/user
