About OrientDB Labs

Want to live on the edge? OrientDB Labs is the place to be. Here you can find all the latest and greatest features of OrientDB, our experiments, cutting edge articles and downloads.


OrientDB 3.0 M2 is finally here!

OrientDB 2.2 was a major overhaul to our previous engine and set the foundation for our next release. Now, with OrientDB 3.0 we’ve build upon our previous version, expanding our multi-model concept even further, unifying graph-document concepts, adding new APIs, and major OrientDB Studio enhancements. We’ve outlined some of the major improvements included in 3.0m2 below. For a complete list of new 3.0 features, improvements and enhancements , take a look at the OrientDB 3.0.0 Milestones release notes. For the moment, This release is limited to the Community Edition of OrientDB 3.0 M2. Enterprise Edition release date is yet to be announced.

As always, we’d like to thank the relentless efforts on behalf of the entire OrientDB Community who have helped make this possible not only by providing feedback & reporting issues but by providing valuable integrations now officially supported in this latest release.

So go ahead and give our latest release a try, but remember, this is not a stable release and is not suitable for production environments.

As this is our milestones release, please submit all bugs or issues via Github.

*Official Documentation currently still under revision and subject to changes.

Community Edition:
No Gremlin support


Community Edition:
Gremlin/TinkerPop 2.6 support


Community Edition:
Gremlin/TinkerPop 3.0 support


Community Edition:
TinkerPop 3 + Spatial Module


Neo4j to OrientDB Importer




  • Graph-document concepts unification in core API: New interface called OElement (to replace ODocument class). As of OrientDB 3.0 any character is allowed as a valid character in property names
  • New database administration API
  • New database access and pooling API
  • The object API now is on a separate module


queries Queries

  • New execution plan based query engine
  • Support for query on remote transactions: This solves the ancient problem when by using a remote connection in the middle of a transaction, queries were executed outside the transaction scope. Now the changes are flushed to the server before to execute the server side query.
  • Support streaming of query result set: Queries are streamed to the client through the remote protocol. This means much less RAM used and less latency because the result is sent immediately during the query execution.


TinkerPop TinkerPop

  • TinkerPop 3.x: Finally the support for TinkerPop 3 is arrived and it’s released as plugin. In this way there is no conflict with the old TinkerPop 2.6 API.
  • TinkerPop 2.x: We know how important is the backward compatibility for our users in production. For this reason we still provide the TinkerPop 2.6 API through a plugin.


security Caching

  • Improvements of storage caching for reduced latency


New DB New Demo Dcustomers_restaurantsB

  • New Demo DB ‘Social Travel Agency': - We bid goodbye to our long lasting “GratefulDeadConcerts” Demo Database which as now been replaced with the new ‘Social Travel Agency’ demo. This demo database provides better examples to help understand OrientDB’s Multi-Model perspective and concepts.


scompatibility Compatibility

OrientDB v3.0 is 90% compatible with code running on OrientDB v2.2.x thanks to the support of the TinkerPop 2.6 API (now as separate module). Main compatibility issues involve the new SQL engine, which is more strict than before, but also significantly smarter and faster.
For a complete list of features, enhancements and supporting documents, take a look at our Official OrientDB 3.0 documentation.*


issues Known Issues

OrientDB 3.0.0-M2 is still under development. The following known issues have currently been reported and are being addressed:

  • The distributed module is still in active development. Please do not use it in 3.0-m2.
  • The Neo4j to OrientDB Importer tool has not been refactored using the new Multi-Model API. As a consequence, if you plan to use the Neo4j to OrientDB Importer, please use it with the CE-TP2 package of OrientDB 3.0. For more information on the available 3.0 packages, please refer to this page.