🗃️Database

Explanation of the transactional database.

WrangleBot uses a self developed transactional database, that saves each change as a single file on the operating system. These transactions can be synced to the Cloud Sync, which will make them canon and all other connected instances will receive the update and execute the change on their live Meta Model.

Please note, that WrangleBot will never delete a transaction file and will only add another transaction that marks previous data as deprecated.

When the database is rebuilt on launch, it will run through all transactions and execute them. This means that active libraries will rebuild MetaFiles or execute meta data changes that are later overwritten etc.

This generally has no impact on performance, as WrangleBot uses an indexing process when rebuilding the Meta Model and it can handle a few hundred thousand transactions with ease.

This system has multiple benefits. Most importantly it allows to back track the provenance of your data. Secondly, it disables destructive actions on your database by default, a huge increase in data integrity. And lastly, it allows multiple instances to co-exist in different locations at the same time.