“AvocadoDB” becomes “ArangoDB”
to avoid legal issues with some other Avocado lovers we have to change the name of our database. We want to stick to Avocados and selected a variety from Mexico/Guatemala called “Arango”.
So in short words: AvocadoDB will become ArangoDB in the next days, everything else remains the same.
We are making great progress towards version 1 (deadline is end of May). The simple query language is finished and documented and the more complex ArangoDB query language (AQL) is mostly done. So stay tuned. And: in case you know someone who is a node.js user and interesting in writing an API for ArangoDB: let me know!
- Additional results for mixed workload
In a comment to the last post, there was a request to conduct some benchmarks with a mixed workload that does not test insert/delete/update/get operations in isolation but when they work together.
- RFC – The ArangoDB/AvocadoDB query language
Note: We changed the name of the database in May 2012. AvocadoDB is now called ArangoDB.
The REST API for AvocadoDB is already available and stable and people are writing APIs using it. Awesome. As...
- Feature preview: batch request API in ArangoDB 1.1
Clients normally send individual operations to ArangoDB in individual HTTP requests. This is straightforward and simple, but has the disadvantage that the network overhead can be significant if many s...