This sample demonstrates the eXtremeDB High Availability binary schema evolution feature. The master application creates and populates the database, then enters a loop creating and deleting objects as it waits for connection requests from replicas. Replica applications create duplicates of the master database, synchronize them with the master database, then receive commit data from the master and perform replication in asynchronous mode. The database schemas are different on master and replica side. The HA subsystem makes the necessary data conversion (binary evolution).
(Note that the eXtremeDB library
mcoha
must be configured withMCO_CFG_BINARY_SCHEMA_EVOLUTION
in order to run this sample.)
See instructions here on how to build this and other samples on your development platform. Once built, the sample can be run from the
\target\bin
directory.In a console window run:
habinev_masterThen in a second console window run:
habinev_replicaBut it is more instructive to run one instance in your development environment debugger, stepping through the code.