SirixDB is an an embeddable, bitemporal, append-only database system and event store, storing immutable lightweight snapshots. It keeps the full history of each resource. Every commit stores a space-efficient snapshot through structural sharing. It is log-structured and never overwrites data. SirixDB uses a novel page-level versioning approach.
As discussed under the issue #537 me and @ElenaSkep would like to propose an enhancement and use apache kafka as an alternative for backend storage.
What it does: Kafka listens to the changes made in a db/resource and stores them in a topic which takes the name of the db.Doing that you can see from the topic of your db the history of all the changes.
Prerequisite:Please download the zip file of apache kafka and run it in the bash with these 2 commands $ bin/zookeeper-server-start.sh config/zookeeper.properties and this $ bin/kafka-server-start.sh config/server.properties.
After that whenever you change something in your db you can see the changes by doing this $ bin/kafka-topics.sh --describe --topic your-db-name --bootstrap-server localhost:9092
As discussed under the issue #537 me and @ElenaSkep would like to propose an enhancement and use apache kafka as an alternative for backend storage.
What it does: Kafka listens to the changes made in a db/resource and stores them in a topic which takes the name of the db.Doing that you can see from the topic of your db the history of all the changes.
Prerequisite:Please download the zip file of apache kafka and run it in the bash with these 2 commands $ bin/zookeeper-server-start.sh config/zookeeper.properties and this $ bin/kafka-server-start.sh config/server.properties.
After that whenever you change something in your db you can see the changes by doing this $ bin/kafka-topics.sh --describe --topic your-db-name --bootstrap-server localhost:9092