OrientDB vs PostgreSQL

This database is primarily, or historically, thought of as a graph database. However, it is actually a multi-model database that supports a variety of noSQL models (key-value, document, etc.).

The Apache 2 license is one of the most liberal licenses. You can use OrientDB for any purpose for free.

Unlike other NoSql databases, OrientDB offers clustering support for free. Furthermore, it's not a basic Master/Slave, but it supports Master-Master replication + Sharding.

It can be queried in a number of ways, but the ability to query with SQL makes it a bit more familiar to use.

OrientDB is incredibly scalable thanks to its multi-master replication. All nodes in a cluster can both read and write.

Full text search support is available when using Lucene based indexing algorithm.

OrientDB is very fast, especially when it comes to relationships between records (or "links").

The Community Edition is free and covers many features, but an Enterprise Edition is available (prices are transparent, published online) with 24x7 support.

PostgreSQL performance increases with each release, this is also proven by many benchmark tests.

Notable performance features include:

• As PostgreSQL only supports one storage engine, it has been able to integrate and optimise it and with the rest of the database. This has resulted in multiple benefits such as the ability to allow different transaction types to co-exist efficiently without the need to select storage engine types once for each table ahead of time.

• On the fly data compression resulting in less IO required for reading.

• Asynchronous + synchronous Replication.

• PostgreSQL supports a asynchronous API for use by client applications. It is reported to increase performance by up to 40% and is not supported by MySQL.

• Designed to scale very well with large numbers of cores at high concurrency levels.

PostgreSQL is known to have a very holistic approach to robustness and data integrity which is reflected by it being fully ACID compliant.

PostgreSQL has always been strict about making sure data is valid before allowing it into the database, and there is no way for a client to bypass those checks.

Depending on your requirements, ACID compliance might be important.

PostgreSQL has a strong community backing it, with guides, tutorials and support for any kind of problem a developer may have.

JSON data can be stored as a column with optional indexes. In 9.4 (upcoming at the time of this writing), JSONB will be a binary version of JSON that will save space. It's like the best of the NO-SQL world without having to give up ACID and Relationships. This means that cascading deletes can be done in a single Transaction across multiple JSON documents.

Regular fixes and features are released

PostgreSQL can be extended to have geographic object support through PostGIS and allows for location queries to be run through SQL.

There are many packages (like Sequelize) that integrate deeply with the features Postgres offers.

Postgres supports popular languages for coding stored procedures, such as Perl and Python. So, you can fairly easy transform just DB-server to reliable Service with complex business logic.

It is a powerful, open source product that has all the bells and whistles when compared with its costly, proprietary counterparts.