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.1 – released 05/29/2014 ✓
  • AQL date and list functions
  • Date and list functions have been added to AQL. This allows you to easily manipulate date and timestamps. You can also flatten result lists and work with static lists.
  • new administration dashboard
  • The new administration dashboard gives you all the information you need about your server healths at a glance. Both in the stand-alone version or a cluster setup.
  • Foxx 1.1
  • Foxx 1.1 comes with a lot of improvements, which allows you to write most tasks in few lines of Javascript code.
  • PHP, .NET, Java, Javascript driver improvements
  • These drivers are now 2.1 ready.
ArangoDB 2.2 – released 02/07/2014 ✓
  • AQL support for modification
  • Finally you can not only use your beloved AQL for reading. It is now also possible to create new documents, replace or update old ones, or remove them completely using AQL to drive your modifications.
  • generalized & transactional graphs
  • We generalized the graph model, so that you can split your vertices and edges into different collections. This allows you to easily group the same kind of vertices into a separate collection for each kind.
  • Foxx 1.2
  • We added all the hooks you need to access various authentication providers from within Foxx applications.
  • Write Ahead Log
  • The internal database engine now supports write-ahead logs to simplify and speed up replication.
ArangoDB 2.3 – released 20/11/2014 ✓
  • query optimizer
  • The query optimizer will be rewritten to take advantage of new indexes and to allow easier rearrangements of execution plans. This gives you better control of the query execution.
  • experimental binary file support
  • We have extended our file support with an experimental binary file support.
  • improved indexes
  • Hash indexes are up to 150 times faster than before.
  • Foxx Queues
  • You will be able to enqueue jobs in Foxx to execute them asynchronously at a later time. Define your own success and error handlers, retry intervals and job types to seamlessly integrate third-party services.
  • Foxx Sessions
  • The Foxx authentication and session system will be rewritten from the ground up to be more modular and customizable for your application’s unique requirements. Adapt the bundled auth, session and user apps to your needs or swap any of them out with your own implementations.
ArangoDB 2.4 – Christmas release ✓
  • Foxx Hypermedia
  • With FoxxGenerator we will introduce a new way to build your own HTTP APIs for ArangoDB which is based upon Foxx: It allows you to define Hypermedia API’s in a descriptive way while still leveraging all features of Foxx including the automatically generated interactive documentation.
  • new V8 version
  • We will upgrade to the newest V8 engine from Google to allow maximal performance and new ECMAScript 6 features.
  • session service
  • Out-of-the-box session management for Foxx-applications and Angular/Ember/Backbone alike.
ArangoDB 2.5 – released 23/02/2015 ✓
  • Sparse Indexes
  • Sparse indexes allow you to ignore null entries, thus saving memory and improving performance dramatically.
  • New ES6 Features
  • All the new lovely stuff: iterators, generators, block scoping, enhanced literals.
  • Improved Foxx Debugging
  • Much better development mode with debugging support you have been waiting for.
  • API Key Management
  • Add API key management to Foxx apps with only a few commands.
ArangoDB 2.6 – released 06/15/2015 ✓
  • improved cursors
  • Removing as many currently locks and moving to C++.
  • additional/improved indexes (sparse)
  • We plan to add or improve the existing indices or add new features. For instance, sparse indexes which only use part of the documents or list indexes which can be used in list attributes.
  • more parallelization
  • Currently queries are executed single threaded. We aim to improve the query optimizer even further, to allow parallel execution of subqueries.
ArangoDB 2.x
  • lock-free cursors
  • Removing as many locks as possible we allow for even better parallelism of queries.
  • additional/improved indexes (list, text, geo, bit-indexes, B-tree)
  • We plan to add or improve the existing indices or add new features.
  • distributed graph algorithms (Pregel)
  • Running distributed graph algorithms for millions of nodes is hard. Googles Pregel framework is a perfect map-reduce-like setup for such use-cases.
  • 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 to deal with arbitrary polygons.
  • Fugu error reporting tool
  • A tool to report and store front-end error messages in a convenient way in a central place.
  • Foxx worker queue
  • Support for long running external processes like sending emails or contacting OAuth providers.
  • 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.
  • 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 fail-over
  • 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.
  • collection level security
  • It will be possible to assign different authorization levels to various collections.

Comments are closed.