Before signing up, please accept our terms & conditions and privacy policy.
What to expect after you signup
You can try out ArangoDB Cloud FREE for 14 days. No credit card required and you are not obligated to keep using ArangoDB Cloud.
At the end of your free trial, enter your credit card details to continue using ArangoDB Cloud.
If you decide that ArangoDB Cloud is not (yet) for you, you can simply leave and come back later.
Estimated reading time: 7 minutes
ArangoDB Oasis, the cloud service of ArangoDB, has been available for a few months now and is growing quickly. The Oasis team got a lot of requests to provide more ways to manage deployments, access policies and other aspects of Oasis.
After adding support for Azure earlier this year, we’re now opening up the Oasis API for all supported cloud providers like Google Cloud and AWS. Read more
Estimated reading time: 6 minutes
Nothing performs faster than arangoimport and arangorestore for bulk loading or massive inserts into ArangoDB. However, if you need to do additional processing on each row inserted, this blog will help with that type of functionality.
If the data source is a streaming solution (such as Kafka, Spark, Flink, etc), where there is a need to transform data before inserting into ArangoDB, this solution will provide insight into that scenario as well. Read more
ArangoDB bundles its regular API Documentation also in Swagger.IO API description format. You can browse and explore it interactively via the ArangoDB Webinterface.
Read more
ArangoDB 2.6 comes with new and changed APIs as well as changed behavior regarding document keys and several graph functions.
If you use Travis-CI for your tests you can download the Travis-CI ArangoDB build here: Travis-CI/ArangoDB-2.6.0-alpha2.tar.gz
The changes so far:
These APIs can be used to perform multi-document lookup and removal operations efficiently. The arguments to these APIs are the name of the collection plus the array of document keys to fetch or remove.
The endpoints for these APIs are as follows:
|
1 2 3 |
PUT /_api/simple/lookup-by-keys PUT /_api/simple/remove-by-keys |
|
1 2 |
curl -X PUT \ http://127.0.0.1:8529/\_db/\_system/_api/simple/lookup-by-keys \ --data '{"collection":"myCollection","keys":["test1","test3"]}' |
documents of the HTTP response. documents is an array containing all documents found. Only those documents that were actually found will be returned. Documents that were searched but do not exist will not be returned and do not trigger any errors. More infoArangoDB can be used as a backend data source for APIs that you compose with the popular open-source LoopBack Node.js framework.
In a recent blog article on StrongLoop, Nicholas Duffy explains how to use his new loopback-connector-arango connector to access ArangoDB:
Getting Started with the Node.js LoopBack Connector for ArangoDB
The tutorial uses the loopback-connector-arango which is available as npm and a demo application which is available from Github. More info
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.
Provided the documents keys are known, all the client application needs to do is to call the collection’s lookupByKeys method:
|
1 2 3 4 5 |
// list of document keys var keys = [ "foo", "bar", "baz", ...]; var results = db.test.lookupByKeys(keys); // now all documents are contained in variable 'results' |
Additionally, the server-side REST API method for bulk document lookups can be invoked directly via HTTP as follows:
|
1 2 3 4 5 |
curl \ -X PUT \ http://127.0.0.1:8529/_api/simple/lookup-by-keys \ --data '{"collection":"test","keys":["foo","bar","baz"]}' |
Jan compared the functionality with single document requests in his latest blog post.
A few weeks ago I wrote about ArangoDB’s specialized export API.
The export API is useful when the goal is to extract all documents from a given collection and to process them outside of ArangoDB.
The export API can provide quick and memory-efficient snapshots of the data in the underlying collection, making it suitable for extract all documents of the collection. It will be able to provide data much faster than with an AQL query that will extract all documents.
In this post I’ll show how to use the export API to extract data and process it with PHP.
Please read the full blog post Exporting Data for Offline Processing.
ArangoDB 2.6 provides a specialized export API for exporting all documents from a collection and shipping them to a client application. It is rather limited but faster than the general-purpose AQL cursor API and can store its snapshots using less memory.
A side effect of the speedup is that the first results will arrive much earlier in the client application. This will help in reducing client connection timeouts in case clients are enforcing them on temporarily non-responding connections. More info