History

Simran 9c7cef5a44 Doc - Update remark about per-database replication (3.4) (#7912 )		2019-01-08 19:36:58 +01:00
..
OtherReplication.md	Doc - Replication Refactor - Part 1 (#4555 )	2018-02-28 12:23:19 +01:00
README.md	Doc - Update remark about per-database replication (3.4) (#7912 )	2019-01-08 19:36:58 +01:00
ReplicationApplier.md	Doc - Replication Refactor - Part 1 (#4555 )	2018-02-28 12:23:19 +01:00
ReplicationDump.md	Doc - Replication Refactor - Part 1 (#4555 )	2018-02-28 12:23:19 +01:00
ReplicationLogger.md	Wal access docs (#6231 )	2018-08-24 09:33:58 +02:00
WALAccess.md	Doc - Internal issue 448 + fix build (#6229 )	2018-08-26 09:32:57 +02:00

README.md

HTTP Interface for Replication

Replication

This is an introduction to ArangoDB's HTTP replication interface. The replication architecture and components are described in more details in Replication.

The HTTP replication interface serves four main purposes:

fetch initial data from a server (e.g. for a backup, or for the initial synchronization of data before starting the continuous replication applier)
querying the state of a master
fetch continuous changes from a master (used for incremental synchronization of changes)
administer the replication applier (starting, stopping, configuring, querying state) on a slave

Please note that if a per-database setup is used (as opposed to server-level replication, available since v3.3.0), then the replication system must be configured individually per database, and replicating the data of multiple databases will require multiple operations.