ArangoDB 2.6 comes with a specialized API for bulk document lookups.
The new API allows fetching multiple documents from the server using a single request, making bulk document retrieval more efficient than when using one request per document to fetch.
The straight-forward implementation of a client application that needs to fetch several documents from an ArangoDB server looks like this:
1 2 3 4 5 6 7 8 9
This works fine but causes excessive HTTP communication between the client application and the server when many documents need to be fetched. In fact, the above code will issue as many HTTP requests as there are documents to fetch.
From the performance point of view, it would be much better to reduce the number of HTTP requests, and retrieve multiple documents from the server in one go, using a single request.
This is where the new document lookup function comes into play. Provided the
documents keys are known, all the client application needs to do is to call the
1 2 3 4 5
Following is a comparison of the execution times for the two different methds. All test runs were conducted in the same ArangoDB 2.6 instance. The tests were run from the ArangoShell. The ArangoShell and the ArangoDB server were located on the same physical host.
1 2 3 4 5
As can be seen, the bulk method can provide a substantial speedup in case lots of documents need to be fetched by their keys at once. The actual speedups might be even higher when using a remote ArangoDB server instead of a localhost connection.
In 2.6 there is currently an ArangoShell implementation for bulk document lookups. Other drivers will follow.
Additionally, the server-side REST API method for bulk document lookups can be invoked directly via HTTP as follows:
1 2 3 4
Restrictions: the bulk document API works only with document keys, not document ids. Additionally, it works on a single collection at a time and cannot be leveraged to fetch documents from multiple collections. Still, a client application can group document keys by collection beforehand and send one bulk request per involved collection. Finally, trying to fetch a document using a non-existing key will not produce an error with the bulk API. Using the one-by-one method, trying to fetch a non-existing document will throw an exception.