Embedding Replication Within an Application

Products > Realtime Data Integration > Embedded Replication

Embedding HVR within an IT Product

For companies which sell a database-based application, replication is a potential business opportunity. Larger customers who use the application could well be interested in the higher availability that a standby database can provide. Or they may want their data piped into a data warehouse in real-time. Both these requirements can be met by offering that customer an HVR-based replication module. This could be priced as a percentage of the cost of the basic application. That way a perceived weakness of the application becomes an extra feature and a new source of revenue.

The phrase "embedding replication" means bundled up replication as module of an existing application package. HVR is ideally suited for embedding. This is because it divides replication into definition and configuration parts. The solution to a replication problem (perhaps horizontal replication or some flavor of collision handling) can be functionally tested before delivery and deployment. A consequence of this is that proper change management principals can be applied.

Hosting a Database Replica

Another possible opportunity for an application vendor is to use HVR to replicate from the customers site to a standby or reporting database hosted at the vendor's own site. The opposite is also possible; hosting the customer's database but replicating to the customer's site. This use of HVR exploits its extreme efficiency over a network. Even with encryption, HVR's network usage is so low it can easily replicate over an existing public network, so no new network links are needed.