This week we pushed some modifications for ArangoDB’s cursor API into the devel branch. The change will result in less copying of AQL query results between the AQL and the HTTP layers. As a positive side effect, this will reduce the amount of garbage collection the built-in V8 has to do.

These modifications should improve the cursor API performance significantly for many cases, while at the same time keeping its REST API stable. Client programs do not need to be adjusted to reap the benefits. In a blog post, Jan shows some first unscientific performance tests comparing the old cursor API with..

This week saw the completion of the AQL UPSERT command. This command will be very helpful in a lot of use cases, including the following:

Max wrote an inspiring article about graphs in data modeling on Medium, packed with his own thoughts – “to sort out some things in my brain” (Max).

He asks and answers the question: Are graphs and graph databases useful in data modeling, and if so, for what and under which circumstances?

In his article, he goes all the way down from the theoretical approach of what is a graph? towards storing a graph in different storage models (RDBMS, document store and graph databases) to querying a graph and finally to his personal conclusion.

This version is deprecated. DOWNLOAD THE NEW VERSION of ArangoDB

A new release of ArangoDB is available for download.

ArangoDB 2.5.1 adds slow-query log and killing running queries to the Http API and to the web-interface. We have also fixed inefficiencies in remove methods of the general-graph module and solved some issues regarding stability on windows. The added option --database.ignore-logfile-errors controls how collection datafiles with a CRC mismatch are treated. We recommend to upgrade your 2.5.0 installation to benefit from these improvements.

ArangoDB 2.5.1 could be started from..

Great to know your database scales and database vendors like ArangoDB add some statistics on node / cluster health directly in their products.

But running a bunch of different servers and applications you need a central hub to collect monitoring data from all services running. In a series of recipes Willi shows how you could easily add monitoring capabilities to NoSQL databases like ArangoDB using collectd with the cURL JSON plugin.

This version is deprecated. Download the new version of ArangoDB

Version 2.5 of ArangoDB makes the development of Foxx based apps a lot easier.

For each of your Foxx apps you could activate the development mode individually, forcing a reread from disk at every request, and providing additional debug output. Set the development mode for an app doesn’t change the mount-point anymore. The Foxx source location on your filesystem is now identical with the mount-point of your app.

This version is deprecated. Download the new version of ArangoDB

If you are interested in NoSQL and come from France, the NoSQL matters conference in Paris is your place to go. ArangoDB contributes with a workshop and a talk and is a silver sponsor of the conference as well. You can meet our team at the exhibition space and ask your ArangoDB questions in person.

Tickets are available for both days, starting at €299 for the conference pass.

On our mailing list, there is quite often the question whether attribute names in objects returned from AQL queries can be made dynamic. Jan discusses in his blog how such dynamic attribute names could be expressed and shows the current implementation that comes with ArangoDB 2.5 – adapting an ES6 proposal that might bring robust dynamic variable names to JavaScript as well.

In ArangoDB 2.5 you will be able to use dynamic variable names as follows:

In the upcoming ArangoDB 2.5 (current devel branch) a new optimizer rule move-calculations-down was added. Jan showcases in his latest blog post how queries with calculations could benefit from this new optimiser rule.