- Active Peer
The term active peer, refers to the initiating peer in any peer-to-peer sync. The active peer initiates the communications. It is the peer that initializes and manages the connection and replication of database changes.
A Checkpoint, in Couchbase Mobile terms, is a “save state” on a replicator, used to enable a restart at the last success-point in the event of a failure during a replication.
The checkpoint itself is a (meta)document that describes how far in the replication process a given replicator has progressed.
Note that two checkpoints are saved for every replication; one local and one remote.
The checkpoint documents are compared at the beginning of every replication. If they do not agree, then it indicates a severe error during the last run, and the replication is forced to restart from the beginning.
- Delta Sync
Delta Sync is the ability to replicate only parts of the Couchbase document that have changed.
This can result in significant savings in bandwidth consumption as well as throughput improvements, especially when network bandwidth is typically constrained.
- Passive Peer
The term Passive peer, refers to the non-initiating peer in any peer-to-peer sync. The passive peer reacts to communications it receives but does not initiate any communication on its own.
- Peer-to-Peer Sync
The term peer-to-peer sync, in the Couchbase Mobile context refers to the synchronization of database changes between Couchbase Lite enabled clients without an intermediary server. Couchbase Lite provides out-of-the-box peer-to-peer sync, over websockets, between Couchbase Lite enabled clients in IP-based networks.
TLSIdentity represents the identity information (Key pair and Certificates) used for setting up TLS Communication.
The TLSIdentity API differs from platform-to-platform.