SirixDB – An Evolutionary, Temporal NoSQL Storage System

Data must be stored in a way, that storage space is used as effectively as possible while supporting the reconstruction of each revision, as it was seen by the database during the commits, in linear time, no matter if it’s the very first revision or the most recent revision. We not only support snapshot based versioning on a record granular level through a novel versioning algorithm called sliding snapshot, but also time travel queries, efficient diffing between revisions and the storage of semi-structured data to name a few. Thus, we are now able send the first GET-request for retrieving the contents of the whole resource again for instance through specifying an simple XPath-query, to select the root-node in all revisions and get the following XPath-result:

In general we support several additional temporal XPath axis:

The same can be achieved through specifying a range of revisions to serialize (start- and end-revision parameters) in the GET-re

Source: github.com