1
0
Fork 0
arangodb/Documentation/Books/Manual/Scalability
Simon 468231efc5 AQL Profiling code (#5165)
* initial start of profiling

* adding profiling code

* Fixing remote block tracing, fixing width and units

* Fixing some tests

* Various fixes

* adressing review comments
2018-04-24 16:17:30 +02:00
..
ActiveFailover AQL Profiling code (#5165) 2018-04-24 16:17:30 +02:00
Cluster Doc - Replication Refactor - Part 1 (#4555) 2018-02-28 12:23:19 +01:00
DC2DC Doc - New Driver Book (#4825) 2018-04-12 17:12:54 +02:00
MasterSlave Doc - Replication Refactor - Part 2 (#4717) 2018-03-02 11:14:53 +01:00
README.md Doc - Replication Refactor - Part 1 (#4555) 2018-02-28 12:23:19 +01:00

README.md

Scalability

ArangoDB is a distributed database supporting multiple data models, and can thus be scaled horizontally, that is, by using many servers, typically based on commodity hardware. This approach not only delivers performance as well as capacity improvements, but also achieves resilience by means of replication and automatic fail-over. Furthermore, one can build systems that scale their capacity dynamically up and down automatically according to demand.

One can also scale ArangoDB vertically, that is, by using ever larger servers. There is no built in limitation in ArangoDB, for example, the server will automatically use more threads if more CPUs are present.

However, scaling vertically has the disadvantage that the costs grow faster than linear with the size of the server, and none of the resilience and dynamical capabilities can be achieved in this way.

Options

Several options are available to scale ArangoDB, each of them has its own pros and cons: