The goal of Replication is to incrementally propagate all changes from one stream (
master) to the other (
slaves- this is done on a stream-by-stream basis
It is supported and quite common to have stream S1 be replicated from TimeBase instance A to instance B, while stream S2 is replicated from B to A.
Replication monitors all changes made to a specific stream (like purge, truncation) and modifies replication target inline with changes.
masterdoes not cause previously replicated purged data to be removed from
- Replication is performed based on a per stream principle: it is not possible to replicate two streams into one and the other way around.
Symbolis a minimal replication unit. Symbol is a
keythat describes time-series (e.g. IoT sensor id)
- Replication is realized in a form of a script written for TickDbShell with all the necessary logic and configurations.
- Replication is supported for all symbols and streams
- TimeBase replication propagates all types of changes, including schema migration.
- Replication may be configured to dynamically support new symbols written to the source stream
Fixed and Dynamic Replication
- In Fixed mode, replication addresses only a fixed list of keys (symbols) (replicate only symbol A and B)
- In Dynamic mode, replication may dynamically pick-up and replicate new keys that are being written to the source stream
Replication supports fail-over and automatic connection restoring.
Backup and Restore
TimeBase Replication supports data Backup and Restore.
- Stream may be replicated to data files - Backup
- Data files can be imported back to TimeBase - Restore
Live Replication Mode
The Live mode maintains an open connection between
slave, where all inserts, updates and deletes are propagated right away.
Live Replication mode applies to all
Durable streams (e.g. from Durable to Transient, from Transient to Transient, from Durable to Durable, from Transient to Durable).
In case Transient stream is involved - it is a Live replication.
Batch Replication Mode
The Batch mode is used to replicate data during off hours.
When replication is run in the Batch mode, it downloads all available changes from the master, closes connection, and stops.
Batch Replication applies to Durable streams (e.g. from Durable to Durable)