ArangoDB 1.4 provides support for multiple databases, a feature often requested by our users. Motivation In the old days, ArangoDB provided the option to create multiple collections, but all collections were created on the same level. As there was no hierarchy of collections, there was a chance of having a collection name clash when using one ArangoDB server for multiple applications. For example, running multiple applications inside the same ArangoDB server did not work if all applications created their own users collections. Workarounds, such as prefixing collection names, were required to make older ArangoDB versions play nicely with multiple applications. With ArangoDB 1.4, multiple databases are supported natively. Workarounds such as prefixing collection names with application names, can go away now.
The bug-fix release 1.4.1 of ArangoDB is available for download. The fixed issues can be found in the changelog. It also fixes a problem with some of the build packages. The arangod daemon process was under some distributions started as root.
We are proud to announce that version 1.4.0 of ArangoDB has been released. The release is available for download here: https://www.arangodb.org/download Thanks to all contributors and testers for your enormous help! Features This release is a major milestone for us, because it contains two of the most wanted features: replication multi-database support It also comes with: Foxx, a lightweight framework for building APIs and applications, see https://www.arangodb.org/manuals/current/UserManualFoxx.html a new and much improved admin web interface, including an intuitive graph browser, see https://www.arangodb.org/manuals/current/NewFeatures14.html#NewFeatures14WebInterface full swagger API documentation, allowing you to easily test and play with the server API using a browser an easy to use import/export tool, see https://www.arangodb.org/manuals/current/NewFeatures14.html#NewFeatures14DumpReload an asynchronous request API (can be used for “fire-and-forget” requests and decrease client waiting time) and several other improvments The complete list of new features can be found here: https://www.arangodb.org/manuals/current/NewFeatures14.html
Packages for the bug-fix release 1.3.3 are now available from our web-site and from Homebrew. For a list of fixes checkout the CHANGELOG.
In ArangoDB’s google group there was recently an interesting discussion on what ArangoDB should offer in terms of replication and sharding. For the rest of you who does not follow the posts in the group, I have copied Frank Celler’s answer into this post: Frank writes: We will start with a master-slave, asynchronous replication for 1.4. This has at least the following advantages: It is a good fit for most use cases. It will allow us to implement backup as “slave”. It easily gives you redundancy by setting up multiple instances. It gives you read-scaling. There are also drawbacks. For example, you need to manually select and switch masters in case of fail-over. However, restricting to a simple solution (which is still hard enough to implement) should allow us to release V1.4 this summer. If you think about MySQL, you will see that in most case a master-slave replication is sufficient. The next step will be master-master replication. This, however, requires more complex protocols like Paxos to elect a master and at least three nodes. We have to decide, if this will be in version 1.5 or maybe already 2.0. We have to see how much has to be changed.
The most recent versions of ArangoDB offer more detailed control over what values will be auto-generated for the _key and _id attributes of documents. They also allow using predictable auto-increment sequences.
We are proud to announce the release of ArangoDB 1.2.0. You can find an overview of the new features in these blog posts: New Features in ArangoDB 1.2 Simplifications in ArangoDB 1.2 API changes in ArangoDB 1.2 If you are upgrading your database from 1.1, please carefully read Upgrading to ArangoDB 1.2 The source code is available from the 1.2 branch on github, the binary packages from our download page. The new version has also been submitted to homebrew and Apple’s AppStore. Last Minute Remarks We have decided to switch the statistics functions off, by default. You can switch them on by changing the config file. The current statistics functions are now obsolescent. We want to switch to a more flexible and less time consuming implementation in 1.3.
Quick note: ArangoDB 1.01 is available. This is a bugfix release. Check the “ArangoDB Google group” for the changelog . By the way – a lot of interesting discussions on ArangoDB, its feature roadmap and how it works in detail, are taking place there. Binaries are always available in the download section.