Hi Marko, for the various instances in an ArangoDB cluster there are 4 distinct roles. Agents, Coordinators, Primary and Secondary DBServers. Please find a brief overview about our cluster architecture here: https://www.arangodb.com/why-arangodb/cluster/
Coordinators (stateless, for query processing and result set building) and DBServers (stateful, holds data) can be split to different nodes and scaled independently or you can let them run both on one instance. You can define this when starting a cluster. In either case you can talk to any coordinator and the coordinator will process your request. If your coming from a relational backround, then the difference - in very simple words is - that you don´t have to know in your application layer on which DBServer the data is stored. The coordinator is an additional layer that handles all of that. You basically just tell any coordinator in your cluster that document X should be written in collection Y and any coordinator will do the rest. Hope I could clarify things. Best, Jan Am Mittwoch, 21. Dezember 2016 12:44:42 UTC+1 schrieb David Marko: > > I could read that ArangoDB supports masters-master replication. But > unfortunately I cant find any relevant information about this feature. > Replication section from docs mentions master-slave only. Is this feature > available in ArangoDB? > -- You received this message because you are subscribed to the Google Groups "ArangoDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
