![]() It is entirely client-side, and doesn’t require a test system to perform any kind of “listening” or network protocol awareness. It does not care how or where the data changes are made.ĭBReplicator expects to run on all the database systems we’ll be supporting. DBReplicator performs as a programming-level abstraction to this process. The replication application (the “middleman”) is entirely responsible for executing the replication protocol and performing replication. ![]() ■ From a Logical Developer’s Perspective: DBReplicator follows this procedure automatically. The replication endpoint then replicates these data changes to the database servers. It also includes the changes that have already been made in the database. In DBReplicator’s case, this request contains the new data to be replicated. ![]() In this way, data changes from a client application can be sent to a remote replication application (which in turn replicates them to the network or database servers). The replication application provides the synchronization mechanism through which the replication endpoint interacts with the database system.Īt the lowest level, DBReplicator simply replicates a “special request” that a client sends to a replication application. DBReplicator’s purpose is to replicate data changes from an application, through a network connection, to an application’s replication endpoint. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |