Are there any design patterns for bitemporal NoSQL databases? [closed]

Question

I'm curious if anyone has implemented or even knows of any bitemporal databases built on NoSQL platforms (e.g., riak).

Answer 1

I don't know of any NoSQL datastore that are specifically designed to handle temporal data. In order to put the valid and transaction time periods onto data in Riak you would need to either:

1. Wrap your documents/values with a structure that can hold metadata like:

   { meta:{ valid:["2001-11-08", "2001-11-09"], transaction:["2011-01-29 10:27:00", "2011-01-29 10:28:00"] } payload:"This is the actual document/value I want to store!" }

2. Create a "meta-document" for each document and use Riak Links to link them up.
   I think this is a little bit cleaner but if you need to retrieve these times often then this method may be too slow.

If you want to retrieve documents by time then I don't think Riak (or any other key/value datastores that I know of) will be the right datastore to use. SQL or possibly some BigTable system may be your only good option.