Frank Celler, Author at ArangoDB - Page 6 of 19

Sign up for ArangoGraph Insights Platform

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.

Getting started with Guacamole on Rails

02API, Documentation, RubyTags: ,

Please note that parts of this article will not work out of the box with ArangoDB 3.0

Using ArangoDB as your main database is a good idea for various reasons. What I personally like about it is its query language AQL. I used relational databases in the past as my main database and writing statements in a language similar to SQL was a great way for me to get started with ArangoDB.

Having a HTTP based interface (like all the cool kids these days) we could build applications running solely on top of our database. That’s rather nice but then we would have to take care of all the gory details. So for our app we want at least an abstraction layer on top of the HTTP API. Better yet, something assisting us with modeling our domain logic.

Meet Guacamole: A object-document-mapper that takes care of all the busywork and allows you to focus on your domain. More info

ArangoDB 2.3.3


This version is deprecated. Download the new version of ArangoDB

A maintenance release for ArangoDB 2.3 is available for download or via your favourite package manager.

Weekly Newsletter, December 11, 2014


ArangoDB Release

We released ArangoDB 2.3.2 with some bug fixes. You can find a full list of changes in our change-log. Here is a short extract:

  • added AQL optimizer rule for removing INTO from a COLLECT statement if not needed
  • fixed missing makeDirectory when fetching a Foxx application from a zip file
  • fixed issue #1173: AQL Editor “Save current query” resets user password

ArangoDB related (Drivers & more)

  • ArangoPy 0.5.3 (Python): Sascha Häusler has updated the Python driver so it is compatible with 2.3
  • ansible-arangodb 1.0.0: Patrick Huber made an install helper, in this case Ansible-Galaxy. Ansible is an IT automation tool. It can configure systems, deploy software, and orchestrate more advanced IT tasks such as continuous deployments or zero downtime rolling updates

Documentation and Cookbook

  • Joins in AQL: How to join documents from several collections. Thanks to Frank Celler

More info

ArangoDB 2.3.2


This version is deprecated. Download the new version of ArangoDB

A maintenance release for ArangoDB 2.3 is available for download or via your favourite package manager.

Building Hypermedia APIs – FoxxGenerator

00API, FoxxTags:

This is the third and final part of Lucas blog series about building hypermedia APIs. In the previous part, we identified the needed transitions and collected some information about each of them. Begin with blog post one to get familiar with concepts on Hypermedia and JSON.

We can now describe the identified transitions using FoxxGenerator. To make the most common case simple, it defaults to the type follow. Therefore defining our four follow transitions is easy using FoxxGenerator:

Note that at this point we are just defining the transitions, we are not adding them to the statemachine we are describing with the help of FoxxGenerator. In the case of creating a book, we need to add additional information. First of, it is a connect transition. Secondly we also need to define the parameters that this transition needs:

More info

Building Hypermedia APIs – a Design Approach using Statecharts

00API, Architecture, FoxxTags:

This is the second blog post on building hypermedia APIs with the focus on API design. In part 1 Lucas describes the concept of links in JSON.

Imagine we have an API where people can like books and other people can then see, who likes a certain book. We want this API to be highly connected: We don’t want to look up URLs in a documentation, we want to follow links as we know it from the world wide web. All we want to do as the author of the API is give our users a single URL from which they can then follow links to all other resources. This is similar to the way we would do this with a website. Leonard Richardson and Mike Amundsen refer to this as the billboard URL for this reason: If you put this URL on some billboard, people know everything to get started with your API. More info

Notes on a busy Month at ArangoDB


November 2014 was a month where our staff (and the cute ArangoDB Foxx) collected lot’s of miles by visiting conferences, meetups and inspiring people in Europe, Africa, the US and Canada. If you missed a talk, there are plenty of slideshares / recordings available.

Release 2.3

Everyone who was not on a plane worked on ArangoDB 2.3 – our major release with a re-written query optimizer that optimizes execution plans, added/improved AQL functions and several performance improvements (@see Query Optimizer Tour by Jan). You can download ArangoDB 2.3.1 and start optimizing.

Frank added a docker file, so you might start shipping ArangoDB in a docker container as well. More info

ArangoDB 2.3.1


This version is deprecated. Download the new version of ArangoDB

A maintenance release for ArangoDB 2.3 is available from our download page and through the package manager.

  • recreate password if missing during upgrade
  • fixed issue #1126
  • fixed non-working subquery index optimizations
  • do not restrict summary of Foxx applications to 60 characters
  • fixed display of “required” path parameters in Foxx application documentation
  • added more optimizations of constants values in AQL FILTER conditions
  • fixed invalid or-to-in optimization for FILTERs containing comparisons with boolean values
  • fixed replication of _graphs collection
  • added AQL functions CALL and APPLY to dynamically call other functions
  • fixed AQL optimizer cost estimation for LIMIT node
  • prevent Foxx queues from permanently writing to the journal even when server is idle
  • fixed AQL COLLECT statement with INTO clause, which copied more variables than v2.2 and thus lead to too much memory consumption. This deals with #1107.
  • fixed AQL COLLECT statement, this concerned every COLLECT statement, only the first group had access to the values of the variables before the COLLECT statement. This deals with #1127.
  • fixed some AQL internals, where sometimes too many items were fetched from upstream in the presence of a LIMIT clause. This should generally improve performance.