Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing SQLite vs OrientDB, the Slant community recommends SQLite for most people. In the question“What are the best databases to use for Node.js applications?” SQLite is ranked 8th while OrientDB is ranked 10th. The most important reason people chose SQLite is:
SQLite is also only 350KiB in size.
Specs
Question Ranking
Pros
Pro Small
SQLite is also only 350KiB in size.
Pro Great language support
SQLite has bindings for a large number of programming languages, including BASIC, Delphi, C, C#, C++, Clipper//Harbour, Common Lisp, Curl, D, Free Pascal, Haskell, Java, JavaScript, Livecode, Lua, newLisp, Objective-C (on OS X and iOS), OCaml, Perl, PHP, Pike, PureBasic, Python, R, REALbasic, REBOL, Ruby, Scheme, Smalltalk, Tcl, Visual Basic.
Pro Self-contained
SQLite is largely self-contained. It requires very minimal support from external libraries or from the operating system.
Pro Portable
An SQLite database is a single ordinary disk file that can be located anywhere in the directory hierarchy. It works by sending requests to a single file where all the data is kept instead of communicating with a hosted database which gives access to an interface by making use of sockets and ports. The file format used is also cross-platform, so can easily be migrated to various machines.
This makes SQLite extremely portable throughout different applications, all that's needed to transfer the whole database is to make a copy of the file.
Pro Great for testing and first stages of development
Because of it's ability to scale and with the portability that a single-file database gives you without losing much of the power and features that SQL gives developers, it's a great choice for testing applications and for the early stages of development when the workload and the data that needs to be stored is not that large.
Pro Not unnecessarily fiddly
Pro Reliable
With less complication, there is less to go wrong.
Pro Zero configuration
There is literally no configuration required to get SQL lite up and running. This is mainly due to SQLite being serverless, there is no separate server process to install, setup, configure, initialize, manage, and troubleshoot.
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.
Cons
Con No multi user
Lacks multi-user capabilities, see SQLite vs. MySQL vs. PostgreSQL: A Comparison of Relational Databases.
Also see: Appropriate Uses For SQLite.
Con Some SQL features are missing
SQLite is made to be extremely lightweight and portable, but it still uses SQL. However, some SQL features such as RIGHT OUTER JOIN and FOR EACH STATEMENT are missing.
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.
