toolarium-temporality-handler

If data is to be stored in a chronological timeline, a corresponding validity is needed in addition to the data. Typically, from / to time stamps are used. This library takes over the entire logic of temporal storage. Temporal actions such as inserting, updating, deleting, terminating etc. of data records are completely implemented.

The backend part must be implemented individually. This is covered by a simple interface IDAOService which contains the methods write, delete and search.

IDAOService<MyObject> daoService = ...
MyObject myObject = ...
TemporalityHandlerFactory.getInstance().getTemporalityHandler().writeTemporlityRecord(myObject), daoService);

The object in the above example must implement the ITemporalityRecord interface. This defines the uniuqe primary key, a data key which is a logical key to the data and the validity information. Please see the test cases where all this is covered.

The following temporality cases are covered:

 Case A: 1) <--(A)-->
         2) <--(A)-->
         
 Case B: 1) <--(A)-->
         2) <--(A)--> <--(B)-->

 Case C: 1)           <--(A)-->
         2) <--(B)--> <--(A)-->

 Case D: 1) <--(A)----->
         2) <--(A)--><--(B)-->

 Case E: 1)       <------(A)-->
         2) <--(B)--><---(A)-->

 Case F: 1) <------(A)-------->
         2) <-(A)-><-(B)-><(A)>

 Case G: 1) <-(A)-><-(B)-><-C->
         2) <-------(D)------->

 Case H: 1) <---(A)--->
         2) <---(A)-->

Built With

• cb - The toolarium common build

Versioning

We use SemVer for versioning. For the versions available, see the tags on this repository.

Gradle:

dependencies {
    implementation "com.github.toolarium:toolarium-temporality-handler:1.0.1"
}

Maven:

<dependency>
    <groupId>com.github.toolarium</groupId>
    <artifactId>toolarium-temporality-handler</artifactId>
    <version>1.0.1</version>
</dependency>