DBMS > OrientDB vs. SQLite vs. Titan vs. Yaacomo

System Properties Comparison OrientDB vs. SQLite vs. Titan vs. Yaacomo

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Titan has been decommisioned after the takeover by Datastax. It will be removed from the DB-Engines ranking. A fork has been open-sourced as JanusGraph.

Yaacomo seems to be discontinued and is removed from the DB-Engines ranking

Description

Multi-model DBMS (Document, Graph, Key/Value)

Widely used embeddable, in-process RDBMS

Titan is a Graph DBMS optimized for distributed clusters.

OpenCL based in-memory RDBMS, designed for efficiently utilizing the hardware via parallel computing

Primary database model

Document store
Graph DBMS
Key-value store

Relational DBMS

Graph DBMS

Relational DBMS

DB-Engines Ranking measures the popularity of database management systems
Trend Chart

Score	3.19
Rank	#93	Overall
	#16	Document stores
	#7	Graph DBMS
	#14	Key-value stores

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

orientdb.org

www.sqlite.org

github.com/thinkaurelius/titan

yaacomo.com

Technical documentation

www.orientdb.com/docs/last/index.html

www.sqlite.org/docs.html

github.com/thinkaurelius/titan/wiki

Developer

OrientDB LTD; CallidusCloud; SAP

Dwayne Richard Hipp

Aurelius, owned by DataStax

Q2WEB GmbH

Initial release

2010

2000

2012

2009

Current release

3.2.29, March 2024

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

Open Source

Apache version 2

Open Source

Public Domain

Open Source

Apache license, version 2.0

commercial

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

Server operating systems

All OS with a Java JDK (>= JDK 6)

server-less

Linux
OS X
Unix
Windows

Android
Linux
Windows

Data scheme

schema-free

Schema can be enforced for whole record ("schema-full") or for some fields only ("schema-hybrid")

yes

dynamic column types

yes

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

yes

XML support

Some form of processing data in XML format, e.g. support for XML data structures, and/or support for XPath, XQuery or XSLT.

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language, no joins

yes

SQL-92 is not fully supported

yes

APIs and other access methods

Tinkerpop technology stack with Blueprints, Gremlin, Pipes
Java API
RESTful HTTP/JSON API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

JDBC
ODBC

Supported programming languages

.Net
C
C#
C++
Clojure
Java
JavaScript
JavaScript (Node.js)
PHP
Python
Ruby
Scala

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Clojure
Java
Python

Server-side scripts

Stored procedures

Java, Javascript

yes

Triggers

Hooks

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

yes

via pluggable storage backends

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

none

yes

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

could be achieved with distributed queries

yes

via Faunus, a graph analytics engine

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

relationship in graphs

yes

Relationships in graph

yes

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

yes

Durability

Support for making data persistent

yes

Supports various storage backends: Cassandra, HBase, Berkeley DB, Akiban, Hazelcast

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

User concepts

Access control

Access rights for users and roles; record level security configurable

User authentification and security via Rexster Graph Server

fine grained access rights according to SQL-standard

More information provided by the system vendor

We invite representatives of system vendors to contact us for updating and extending the system information,
and for displaying vendor-provided information such as key customers, competitive advantages and market metrics.