Enterprise Edition
Chronicle QBM Replication is included in Chronicle Queue Enterprise, which is commercially supported. Key features include:
Real-time replication to provide continuous backup of all your map data.
Resilience features to support robust failover and disaster recovery.
Full support from Chronicle Software’s technical experts.
For more information, see Chronicle Queue Enterprise.
Replication
Chronicle Queue Enterprise enables replication of Chronicle Maps over TCP/IP. (for more details see Chronicle Queue Enterprise Replication).
TCP Background
TCP/IP is a reliable protocol, ensuring data delivery unless there is a network failure or hardware outage.
How Chronicle QBM Replication works
An underlying Chronicle Queue persists changes to the Map. These changes are replicated using Chronicle Queue Enterprise to one or more additional Chronicle Maps. If needed, a single underlying queue can be shared by multiple Maps. Replication does not block Map get or put operations.
Maps can be configured as either a source or a sink. The source Map sends changes, while sink Maps receive them. Replication flows from source to sink, and a slow or offline sink will not affect the performance of other sinks or the source Map.
If a node goes offline, it will automatically rejoin the cluster, handshake, and synchronize with the cluster when it comes back online. The application can be notified once synchronization is complete and the sink Map is up to date and replicating live.
A new node can be added easily by connecting it to the cluster. The new sink Map will then be hydrated from the cluster automatically.
The source Map can be changed if necessary. For example, if the master host or data center changes, the cluster can typically be reconfigured with a new source in just milliseconds, allowing replication to restart quickly.