arangodb

History

Simran Brucherseifer e4eeb57e30 Docs: Use standard Markdown notation for headlines and disable MarkdownPP		2016-12-06 02:41:58 +01:00
..
OtherReplication.mdpp	Docs: Use standard Markdown notation for headlines and disable MarkdownPP	2016-12-06 02:41:58 +01:00
README.mdpp	Docs: Use standard Markdown notation for headlines and disable MarkdownPP	2016-12-06 02:41:58 +01:00
ReplicationApplier.mdpp	Docs: Use standard Markdown notation for headlines and disable MarkdownPP	2016-12-06 02:41:58 +01:00
ReplicationDump.mdpp	Docs: Use standard Markdown notation for headlines and disable MarkdownPP	2016-12-06 02:41:58 +01:00
ReplicationLogger.mdpp	Docs: Use standard Markdown notation for headlines and disable MarkdownPP	2016-12-06 02:41:58 +01:00

README.mdpp

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](../../Manual/Administration/Replication/index.html).

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 all replication operations work on a per-database level. If an 
ArangoDB server contains more than one database, the replication system must be
configured individually per database, and replicating the data of multiple
databases will require multiple operations.