DBMS > JanusGraph vs. OrigoDB vs. Tarantool vs. TerminusDB

System Properties Comparison JanusGraph vs. OrigoDB vs. Tarantool vs. TerminusDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A Graph DBMS optimized for distributed clusters

It was forked from the latest code base of Titan in January 2017

A fully ACID in-memory object graph database

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Primary database model

Graph DBMS

Document store
Object oriented DBMS

Document store
Key-value store
Relational DBMS

Graph DBMS

Secondary database models

Spatial DBMS

with Tarantool/GIS extension

Document store
RDF store

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

Score	2.02
Rank	#125	Overall
	#12	Graph DBMS

Score	0.06
Rank	#380	Overall
	#50	Document stores
	#18	Object oriented DBMS

Score	1.67
Rank	#143	Overall
	#25	Document stores
	#25	Key-value stores
	#65	Relational DBMS

Score	0.23
Rank	#316	Overall
	#27	Graph DBMS

Website

Technical documentation

docs.janusgraph.org

origodb.com/docs

www.tarantool.io/en/doc

terminusdb.github.io/terminusdb/#

Developer

Linux Foundation; originally developed as Titan by Aurelius

Robert Friberg et al

DataChemist Ltd.

Initial release

2017

2009

under the name LiveDB

2008

2018

Current release

0.6.3, February 2023

2.10.0, May 2022

11.0.0, January 2023

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

Open Source

GPL V3

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

C and C++

Prolog, Rust

Server operating systems

Linux
OS X
Unix
Windows

Linux
Windows

BSD
Linux
macOS

Linux

Data scheme

yes

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

yes

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

string, double, decimal, uuid, integer, blob, boolean, datetime

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.

can be achieved using .NET

Secondary indexes

yes

SQL

Support of SQL

Full-featured ANSI SQL support

SQL-like query language (WOQL)

APIs and other access methods

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

.NET Client API
HTTP API
LINQ

Open binary protocol

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

Clojure
Java
Python

.Net

C
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

JavaScript
Python

Server-side scripts

Stored procedures

yes

Lua, C and SQL stored procedures

yes

Triggers

yes

Domain Events

yes, before/after data modification events, on replication events, client session events

yes

Partitioning methods

Methods for storing different data on different nodes

yes

depending on the used storage backend (e.g. Cassandra, HBase, BerkeleyDB)

horizontal partitioning

client side managed; servers are not synchronized

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

Journaling Streams

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Faunus, a graph analytics engine

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

Foreign keys

Referential integrity

yes

Relationships in graphs

depending on model

yes

Transaction concepts

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

ACID

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, cooperative multitasking

yes

Durability

Support for making data persistent

yes

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

yes

Write ahead log

yes, write ahead logging

yes

in-memory journaling

In-memory capabilities

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

yes

yes, full featured in-memory storage engine with persistence

User concepts

Access control

User authentification and security via Rexster Graph Server

Role based authorization

Access Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
Users and Roles

Role-based access control

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

Data processing speed and reliability: in-memory synchronous replication
9 November 2021, Vladimir Perepelytsya, Tarantool (sponsor)

show all

Recent citations in the news

Database Deep Dives: JanusGraph
8 August 2019, ibm.com

JanusGraph Picks Up Where TitanDB Left Off
13 January 2017, Datanami

From graph db to graph embedding. In 7 simple steps. | by Andy Greatorex
30 July 2020, Towards Data Science

Nordstrom Builds Flexible Backend Ops with Kubernetes, Spark and JanusGraph
3 October 2019, The New Stack

The year of the graph: Getting graphic, going native, reshaping the landscape
8 January 2018, ZDNet

provided by Google News

Deploying Tarantool Cartridge applications with zero effort (Part 1)
16 December 2019, Хабр

VShard — horizontal scaling in Tarantool
7 March 2019, Хабр

Accelerating PHP connectors for Tarantool using Async, Swoole, and Parallel
18 December 2019, Хабр

provided by Google News

How TerminusDB is commercializing its open source graph database
16 March 2021, VentureBeat

TerminusDB Takes on Data Collaboration with a git-Like Approach
1 December 2020, The New Stack

Trinity College spinout TerminusDB secures €3.6m in investment
15 March 2021, The Irish Times

[MCR2030-CAMS-ARISE-UNDRR Webinar] Preventing cascading failures of critical assets: Using the Open-Source ...
12 April 2022, United Nations Office for Disaster Risk Reduction

Irish start-ups received €28m from Enterprise Ireland in 2021
7 April 2022, SiliconRepublic.com

provided by Google News

Share this page