Estimated reading time: 1 minute

Today we are excited to announce that ArangoGraph, the ArangoDB Managed Service, is available for purchase in the AWS Marketplace. With this announcement, ArangoGraph can now be purchased directly via both AWS and GCP.

The AWS Marketplace provides an extensive catalog of software solutions for users to easily explore, test, buy, and deploy on AWS. If you’re an AWS customer, here’s what this announcement means for you:

We are working on the release of ArangoDB 3.6 and today, just in time for the holiday season, we reached the milestone of RC2. You can download and take the RC2 for a spin: Community Edition and Enterprise Edition.

The next version of the multi-model database will be primarily focused on major performance improvements. We have improved on many fronts of speeding up AQL and worked on things like:

• Subquery performance
• Parallel execution of AQL queries that allows to significantly reduce gathering time of data distributed over several nodes
• Late document materialization that reduces the need..

We are closing in on the general availability of ArangoDB 3.5. With this (hopefully) last release candidate for the new version, we want to highlight a pretty neat new feature, which many of you requested – a much simpler way to use ACID transactions without the need to write any Javascript code.

Get the latest Releaseof ArangoDB 3.5: Community and Enterprise.

Before we dive in, we want to send another big THANK YOU to the many Avocaderas and Avocaderos who took the release candidates for a spin and shared their findings with us. Immensely helpful for the whole team to learn where we were..

Ready for some hot new stuff? 🙂

Today we can share Release Candidate 3 of ArangoDB 3.5 with you and have a world premier up our sleeves.

Get the Enterprise edition of ArangoDB 3.5.

With this RC we want to highlight a brand new feature which we called SmartJoins (well, no… this name was actually not born in the marketing department).

SmartJoins allows users to shard multiple collections in a, well, smarter way. Join operations among huge distributed collections can run much more efficiently now and performance gets very close to a single instance. More on SmartJoins and a hands-on tutorial..

For ArangoDB 3.4 we already added 100,000 lines of code, happily deleted 50,000 lines and changed over 13,000 files until today. We merged countless PRs, invested months of problem solving, hacking, testing, hacking and testing again and are super excited to share the feature complete RC1 of ArangoDB 3.4 with you today.

Download the technical preview package for your OS: RC1 3.4 Community and RC1 3.4 Enterprise.

The team implemented over 40 new features, improvements and optimizations. In this short post, we will highlight just a few of them. You can find a full list in the release notes and..

Our recent release 3.3.9 includes several performance optimizations for data retrieval cases. Benefits can be expected for both storage engines, MMFiles and RocksDB, AQL batch lookup queries, and cluster AQL queries.

Version 6.0.0 of the JavaScript driver arangojs is now available (Find it on GitHub).

This is a major release that introduces a small number of breaking changes so make sure to check out the arangojs changelog before upgrading. The most significant additions in this release are support for load balancing and automated failover as well as improved browser and TypeScript support.

Just in time for the holidays we have a nice present for you all – ArangoDB 3.3. This release focuses on replication, resilience, stability and thus on general readiness for your production small and very large use cases. There are improvements for the community as well as for the Enterprise Edition. We sincerely hope to have found the right balance between them.

It is all about improving replication. ArangoDB 3.3 comes with two new exciting features: data-center to data-center replication for clusters and a much improved active-passive mode for single-servers. ArangoDB 3.3 focuses on replications and improvements in this area and provides a much better user-experience when setting up a resilient single-servers with automatic failover.