When comparing OrientDB vs MySQL with InnoDB, the Slant community recommends MySQL with InnoDB for most people. In the question“What are the best ACID-compliant scalable databases?” MySQL with InnoDB is ranked 3rd while OrientDB is ranked 5th. The most important reason people chose MySQL with InnoDB is:
Some of these APIs include ODBC, Java (JDBC), Perl, Python, PHP, Ruby, and native C. Also, there are a number of third party APIs that are available for use to interact with the database
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Multi-model database (document, object, graph)
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.).
Pro Open Source commercial friendly license (Apache 2)
The Apache 2 license is one of the most liberal licenses. You can use OrientDB for any purpose for free.
Pro Free clustering support
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.
Pro Distributed Graph Database with relational type Documents
Pro Supports sql as well as other query languages
It can be queried in a number of ways, but the ability to query with SQL makes it a bit more familiar to use.
Pro Multi-master replication
OrientDB is incredibly scalable thanks to its multi-master replication. All nodes in a cluster can both read and write.
Pro Full text search
Full text search support is available when using Lucene based indexing algorithm.
Pro Performance
OrientDB is very fast, especially when it comes to relationships between records (or "links").
Pro Enterprise version available
The Community Edition is free and covers many features, but an Enterprise Edition is available (prices are transparent, published online) with 24x7 support.
Pro Multiple APIs
Some of these APIs include ODBC, Java (JDBC), Perl, Python, PHP, Ruby, and native C. Also, there are a number of third party APIs that are available for use to interact with the database
Pro Many applications available
There are a number of applications that are built with the focus of MySQL. Some of these include Drupal, Joomla, Wordpress and more.
Pro Scalable
Works well under simple operations or heavy tasks.
Pro Huge community support
Being the world's most popular open source database means there are tons of available examples and information for users' to access.
Cons
Con Not well known
It's a very unfortunate thing, but it's true. Not many people know of this gem so that makes it difficult to find community support at times. It also makes it hard to get people on board with it who shop products by brand name or flashy marketing. It also means there are fewer code snippets, libraries, and frameworks that consider it. While it's interoperability is good with SQL support and Tinkerpop, it still doesn't change the fact that many things don't give it much thought and that can lead to more work as a developer sometimes.
Con Learning curve
A lot of effort went into making OrientDB easy and familiar to use (such as SQL queries for example). However, it's important to understand the database engine a bit and how it works in general (links for example). This involves a bit of a learning curve if you're not familiar with graph databases. Not an enormous curve or anything, but it's still a consideration.
Con Bulk inserts may cause an out of memory crash
When doing inserts in OrientDB you have to be careful to do them one at a time. Bulk inserts may cause out of memory error
.
Con InnoDB is not fully configured
When you initially install MySQL, InnoDB needs to be configured to make it suite your needs and there are many issues you can come across.