Any release date can be changed at any time. This is not a promise but just the current schedule.

Our current planned features for the next releases are:

ArangoDB 2.7 – released 09/10/2015 ✓
  • Replication Improvements
  • This allows much easier synchronization of a single collection from a master to a slave server.
  • Throughput Enhancements
  • A lot is not enough. Throughput is another key requirement for a premium database. Again we pushed our throughput a big step forward with 2.7.
  • Improved Date Handling in AQL
  • AQL functions for date and time calculation and manipulation.
  • Index Buckets
  • Split primary indexes and hash indexes into multiple index buckets.
ArangoDB 2.8 – released 25/01/2016 ✓
  • Array Indexes
  • Hash indexes and skiplist indexes support array values so they index individual array members.
  • Graph Traversals in AQL
  • Using AQL to traverse a graph / edge collections.
  • AQL Optimization
  • Reimplemented AQL functions in C++ for improved performance.
  • New Framework in Mesosphere DCOS 1.3
  • ArangoDB package for DCOS 1.3, enhanced replication and failover.
  • Automatic Deadlock Detection for Transactions
  • The new deadlock detection mechanism will kick in automatically when it detects operations that are mutually waiting for each other.
ArangoDB 3.0
  • VelocyPack
  • Internal storage will change from JSON to VelocyPack for enhanced performance, smaller footprint and binary support.
  • Persistent Indexes
  • We plan on making indexes persistent, which will allow using quicker recovery, start-up and larger datasets.
  • Automatic Failover with Mesos
  • This release will contain the next iteration of our Mesosphere DCOS integration and will thus offer convenient set-up of synchronous replication and full automatic failover.
ArangoDB 3.x
  • Low-Level C++ Driver
  • Implementation of efficient, reusable, platform-independent core driver functionality to be used in multiple client languages.
  • Automatic Rebalance
  • It will be possible to utilize storage among multiple machines automatically.
  • Lock-free Cursors
  • Removing as many locks as possible will allow for even better parallelism of queries.
  • Improved Indexes (array, text, geo)
  • We plan to add or improve the existing indexes or add new features.
  • Auto-failover
  • Allow for automatic failover to slave nodes. A monitor process detects network failures and automatically switches to backup nodes.
  • Zero Administration
  • Reduces the administration cost as much as possible.
  • General Geo Functions
  • General geo functions help you deal with arbitrary polygons.
  • Master/Master Replication
  • Replicate data not just in a master/slave fashion, but also as true master/master.
  • HTTP 2.0 and/or WebSockets
  • Support for new Web-protocols like HTTP 2.0 or WebSockets.
  • Collection Level Security
  • It will be possible to assign different authorization levels to various collections.
  • Health Check Dashboard in Mesos
  • Enables you to see the health status of your ArangoDB cluster in Mesos dashboard.
  • Cluster Dashboard
  • Improved cluster administration will be implemented.
  • Vertex-centric Indexes
  • Vertex-centric indexes allow you to handle near neighbors very fast.
  • Data Compression
  • Allow to compress big text fields to trade time for memory.
  • Distributed Failover
  • Instead of dedicated slave, you can use spare capacity on masters to hold the slave for other shards.
  • Constraints
  • Define constrains on your collection, in order to valid data entered.
  • Trigger
  • Trigger a Javascript function as soon as a modification occurs.
  • Binary Data
  • Support for big data blobs.
  • Distributed Transaction
  • Transactions in a distributed environment with a transaction manager.
  • Range Sharding
  • Instead of sharding based on a hash value, allow to shard ranges.

Comments are closed.