The Replication framework's goal is to offer the xmlBlaster user a way to replicate data from one or several source databases to one or more sink databases. The framework has been designed for a single-master / multi-slave approach. What does that mean ? It means that it does not offer any conflict resolution mechanism. In other words it is safe for cases where you have one single master database, also called the source for the replication, and one or more slaves, also called the sinks of the replication or replicas. It will generally not be safe where you have more than one master.
There are situations where this framework is currently used with more than one source for one sink, but there are limitations. For example you must ensure that the same data (at least on a row granularity) always comes from one single source.
The following are some of the features which the replication Framework offers:
Master / Multi Slave approach
Conventional one to one Replication
Replication with Data Manipulation on a per sink individual basis with no intervention on the master side
Replication with Data Filtration on a per sink individual basis with no intervention on the master side
Use of all Communication Protocols offered by XmlBlaster (even the most fancy ones)
Persistence of Messages, Fail over and guaranteed sequence of messages
Transactions are handled atomically and sent in a single Message
Possibility to interchange this with other sources/sinks for for example Meta-Databases
Plugin approach to allow business-specific functionality
Possibility to intermix different database versions and vendors
Performance tuning for specific vendors (for example for initial update)
Highly Compressed communication
Encrypted and secure replication
Unlimited number of sinks
Efficient and reliable even on unreliable networks