This sample demonstrates the transaction window feature. The transaction window allows setting the size of the transaction packet. The replica sends a reply only once per transaction packet. Non-yet-confirmed transactions are saved on the master side.
The master application creates and populates the database, then enters a loop creating, updating and deleting objects as it waits for connection requests from replicas. The master switches the transaction window size from 1 to 1000 to demonstrate the performance gain.
Replica applications create duplicates of the master database, synchronize them with the master database, then receive commit data from the master and perform replication.
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:
hawindow_masterThen in a second console window run:
hawindow_replicaBut it is more instructive to run one instance in your development environment debugger, stepping through the code.