Released OrientDB v 1.6.1: bugs fixed and some improvements in performance

Orient Technologies has released OrientDB v1.6.1. This is a hot-fix for v1.6 so this email will be shorter than usual.

To download it goto

What’s new
  • Starting from 1.6.1 OrientDB is distributed in 2 ways:
    • TAR.GZ for Linux, MacOSX and Unix in general
    • ZIP for Windows users
  • Studio plugin is bundled in server/plugins directory
  • The build process now generates a 100% complete OrientDB installation, so get the source code from GitHub ( and execute “ant clean install”. Now the GratefulDeadConcerts database is automatically generated.
  • We’ve improved performance with SBTree indexes and plocal in general
Full list of closed issues

Next Online course

Do you wish to attendee a OrientDB course, but you can’t get 2 entire days off? Well, we’ve created a new format for the Online course, the “A week in Graphs” course. about 2 hours each day for 5 days. Apply now to the December edition to get the Early Bird price:

Have fun with Graphs,

Luca Garulli
CEO at Orient Technologies
the Company behind OrientDB

OrientDB becomes Distributed using Hazelcast, Leading Open Source In-Memory Data Grid
Elastic Distributed scalability added to OrientDB, a Graph Database that support hybrid Document Database features
London, UK – Orient Technologies ( and Hazelcast ( today announced that OrientDB has gained a multi-master replication feature powered by Hazelcast.
Clustering multiple server nodes is the most significant feature of OrientDB 1.6. Databases can be replicated across heterogeneous server nodes in multi-master mode achieving the best of scalability and performance.
“I think one of the added value of OrientDB against all the NoSQL products is the usage of Hazelcast while most of the others use Yahoo ZooKeeper to manage the cluster (discovery, split brain network, etc) and something else for the transport layer.” said Luca Garulli, CEO of Orient Technologies. “With ZooKeeper configuration is a nightmare, while Hazelcast let you to add OrientDB servers with ZERO configuration. This has been a big advantage for our clients and everything is much more ‘elastic’, specially when deployed on the Cloud. We’ve used Hazelcast not only for the auto-discovery, but also for the transport layer. Thanks to this new architecture all our clients can scale up horizontally by adding new servers without stopping or reconfigure the cluster”.
“We are amazed by the speed with which OrientDB has adopted Hazelcast and we are delighted to see such excellent technologists teaming up with Hazelcast.” said Talip Ozturk, CEO of Hazelcast. “We work hard to make the best open source in-memory data grid on the market and are happy to see it being used in this way.”
Both Hazelcast and Orient Technologies are providing professional open source support to their respective projects under the Apache software license.
About Orient Technologies
Orient Technologies is the company behind the NoSQL project OrientDB, the Graph Database with a hybrid model taken from both the Document Database and Object Orientation worlds. OrientDB is FREE for any purpose even commercial because is released under the Apache2 License. Orient Technologies offers commercial services against OrientDB for companies who want supporttraining and consulting.
About Hazelcast
Hazelcast ( develops, distributes and supports the leading open source in-memory data grid. The product, also called Hazelcast, is a free open source download under the Apache license that any developer can include in minutes to enable them to build elegantly simple mission-critical, transactional, and terascale in-memory applications. The company provides commercially licensed Enterprise editions, Hazelcast Management Console and professional open source training, development support and deployment support. The company is privately held and headquartered in Palo Alto, California.
Keywords: Hazelcast, In-memory data grid, Document Database, Object Database, In-memory Database, computing, big data, NoSQL, grid computing, Apache License, Open Source

Happy Halloween! Trick or Treat?

Orient Technologies has just released OrientDB v1.6.

What’s new? First of all we joined the Standard Edition and Graph Edition in just “Community Edition“. By default it contains all the components to use OrientDB as Graph Database. if you want to use it as embedded as pure Document Database just link the needed jars only.

Community Edition

Community Edition means the FREE version of OrientDB with all the features you already knows and something news:
  • SBTree: new index engine with the support for transactions and range queries
  • Distributed: new Architecture based on Hazelcast, new Distributed Transaction support across nodes, new Database Sharding feature
  • Studio: total rewriting in a new tool hosted on separate project
  • HTTP: execute commands in batch mode, partial document updates, JSON as return of create and update documents, management of multi databases in the same connection
  • Scripts: new “Orient” variable to get database instances, new switchUser() API to change current user
  • Plugins: new hot deployment plugin as folders, zip and jar files
  • SQL: new target “metadata” to retrieve schema and indexes
  • Console: new silent mode
  • Many features and performance improvements on plocal and hash indexes
  • Bug fixing
Full list of closed issues

Enterprise Edition

This Edition is commercial licensed and it’s based on Community Edition with additional features like:
  • Workbench, as a centralized cockpit to manage multiple servers
  • SQL Profiler, to tune the database based on usage patterns
  • Metric Analyzer, to monitor and analyze metrics
  • Configurable Alerts, to get notified when a node is unreachable or when a metric breaks a configurable threshold
  • Production support available on demand (see below)
Enterprise Edition costs £ 1,000.00 per server/year or £ 500,00 for startups. For more information goto: Enterprise Edition.

Production Support

Starting form v1.6 Orient Technologies gives support only against Enterprise Editions that are tested on multiple platforms and certified. 

If you purchase the Production Support, the Enterprise Edition is FREE.


All the pending major/critical issues will be fixed in hot-fix releases (like 1.6.1, 1.6.2, etc.) planned about every week if needed.

Have fun tonight with ghosts and graphs!

Luca Garulli
CEO at Orient Technologies
the Company behind OrientDB

London, October 22 2013

OrientDB is the first GraphDB in the Gartner Operational DBMS Magic Quadrant!

This is the link to the report:

(The report is available only for Gartner clients)

Hi all,
we’re glad to announce in the “develop” branch (1.6.0-SNAPSHOT) the new distirbuted configuration engine that doesn’t use Hazelcast’s Executor Service but rather Queues. This made the entire work easier (we dropped 50% of code of previous implementation) achieving better performances.
This is the new configuration in orientdb-dserver-config.xml:

value="com.orientechnologies.orient.server.distributed.conflict.ODefaultReplicationConflictResolver" />

value="com.orientechnologies.orient.server.hazelcast.sharding.strategy.ORoundRobinPartitioninStrategy" />

As you can see we don’t use realignment tasks anymore: when a node comes up it get the pending messages from Hazelcast queue. This is good when a server goes up & down in a reasonable time like for a temporary network failure or an upgrade of a server. In case you plan to stop and restart the server after days you’d need to re-deploy the entire database on the server.
This is the default configuration in the new default-distributed-db-config.json file, put it under $ORIENTDB_HOME/config and remove that contained under the database if any. This configuration comes with only one partition where new joining nodes auto register themselves. So this means all the nodes have the entire database (no partitioning). To achieve better performance avoid to use a writeQuorum bigger than 2. I think having 2 servers that synchronously have the data it’s very secure. However all the server in the partition are updated, just the client receives the response when writeQuorum is reached. This is the new default configuration file:
"replication": true,
"clusters": {
"internal": {
"replication": false
"index": {
"replication": false
"ODistributedConflict": {
"replication": false
"*": {
"replication": true,
"writeQuorum": 2,
"partitioning": {
"strategy": "round-robin",
"default": 0,
"partitions": [
[ "" ]

Partitions contains an array of partitions as node names. The keyword “<NEW_NODE>” means that new node that joins the cluster are automatically added in that partition. 
So if you start X nodes the replication works out of the box. Thanks to the partitioning you can shard your database across multiple nodes avoiding to have a symmetric replica. So you can use your 6 servers as before:
  [ “node0”, “node1”, “node2”,  “node3”, “node4”, “node5” ]
or in this way:
  [ “node0”, “node1”, “node2” ],
  [ “node3”, “node4”, “node5” ]
It’s like RAID. With this configuration you’ve 2 partitions (0 and 1) with 3 replica each. So the database is spanned across 2 partitions automatically that means each partition owns about half database. By default we provide the “round-robin” strategy but you can already plug your one to better split the graph following your domain.
This is part of the Sharding feature, so consider it as a preview. It will be available in the next release (1.7 or 2.0).
Furthermore we’ve introduced variable timeouts that change based on the runtime configuration (number of nodes, type of replicated command, etc.)
We’ve also introduced new settings to tune the replication engine (OGlobalConfiguration class):
DISTRIBUTED_THREAD_QUEUE_SIZE(“distributed.threadQueueSize”, “Size of the queue for internal thread dispatching”, Integer.class,

DISTRIBUTED_CRUD_TASK_TIMEOUT(“distributed.crudTaskTimeout”, “Maximum timeout in milliseconds to wait for CRUD remote tasks”,
      Integer.class, 3000),
      “Maximum timeout in milliseconds to wait for Command remote tasks”, Integer.class, 5000),

DISTRIBUTED_QUEUE_TIMEOUT(“distributed.queueTimeout”, “Maximum timeout in milliseconds to wait for the response in replication”,
      Integer.class, 3000),
      “Maximum timeout in milliseconds to collect all the synchronous responses from replication”, Integer.class, 5000),
      “Maximum timeout in milliseconds to collect all the asynchronous responses from replication”, Integer.class, 15000),

      “Maximum timeout in milliseconds to collect all the asynchronous responses from replication”, Integer.class, 15000);
I suggest to everybody is using the distributed architecture to upgrade to 1.6.0-SNAPSHOT and:
– update the file orientdb-dserver-config.xml and !
– update the file default-distributed-db-config.json
– remove the previous file default-distributed-db-config.json under the databases/ directory
We successfully tested the new engine against 10 servers and 200 connected clients with a writeQuorum=2 (2 synchronous copy before to give the OK to the client).
Next week we’ll release OrientDB 1.6, so you’ve last chance to vote your bugs to be in 1.6 roadmap!
Luca Garulli
CEO at Orient Technologies
the Company behind OrientDB

London, September 21th 2013

NuvolaBase, the Orient Technologies division that offered OrientDB as “Database As A Service” (DaaS), announces to stop its activity. In this way Orient Technologies company will be more focused against OrientDB on development, support, consultancy and training.

All the paying clients will be hold for FREE for +6 months after the expiration of their contracts to give them the time to switch to another solution.

What about the alternatives?

We suggest to install OrientDB Open Source Graph Database on top of a Virtual Machine hosted at any Cloud Provider like AWS.

NuvolaBase Team

London, September 2nd 2013

Mr. Claudio Tesoriero is the author of “Getting Started with OrientDB”, the new book about OrientDB. Claudio is a certified OrientDB developer that wrote this book for all the developers that want to start working with OrientDB NoSQL database.

Take a look at the Table of Contents:

Chapter 1: Installing OrientDB

Chapter 2: Administering OrientDB

Chapter 4: Performance Tuning

Chapter 5: Advanced Features

London, August 27, 2013 

Orient Technologies changed the online courses by providing a new format: 9 hours in 2 days, instead of 7 hours in only one day.  The cost of the course remains the same: £ 300.00 per attendee.

The 9 hours are split into 2 days of 4 hours each with an additional hour of off-line exercises after the first day. This change is the fruit of all the feedback received from past events where attendees reported to us that the covered topics were too many to be covered in only one day with 7 hours of non-stop learning.
We also removed the Document and Object database API portions in order to be more focused on the Blueprints API and the Graph Database concepts.

If you’re interested in taking a course, please go to:

Luca Garulli
CEO at Orient Technologies
the Company behind OrientDB

Hi everyone,
only 2 months after the release of v.1.4 (and only 1 month after the v.1.4.1 release), version 1.5 is now available for download!  

This release could actually be named 2.0 for all the various new features:

  • New PLOCAL (Paginated Local) storage engine.  In comparison with LOCAL, it’s more durable (no usage of MMAP) and supports better concurrency on parallel transactions.
  • New Hash Index type with better performance on lookups. It does not support ranges.
  • New “transactional” SQL command to execute commands inside a transaction. This is useful for the “create edge” SQL command, in order to avoid corruption of the graph
  • Import now migrates RIDs, allowing the ability to import database objects in a different one from the original 
  • Breadth first” strategy added on traversing (Java andSQL APIs)
  • Server can limit maximum live connections (to prevent DOS)
  • Fetch plan support in SQL statements and in binary protocol for synchronous commands too
  • Various bug fixes

For all the issues:

For more information about the release:

To receive Professional Support, please contact us at:

Special thanks goes out to Artem Orobets, who just joined the Orient Technologies company, to Andrey Lomakin who has coordinated and co-developed the new PLOCAL, Hash Index and many other features on the engine part. Thanks to Luca Molino who is back on the Object Database interface. Thanks to all the contributors with their pull requests, test cases and issues who have contributed to improving OrientDB. Thanks also to the TinkerPop team for providing such cool technology to stack on top of OrientDB.

Luca Garulli
CEO at Orient Technologies
the Company behind OrientDB

It’s official: Orient Technologies LTD is the new company that will manage OrientDB software and services. NuvolaBase company has been incorporated as division to manage the DAAS (Database As A Service) on the Cloud.

Start using the world’s leading multi-model database today