DBMS > JanusGraph vs. OpenQM vs. OrigoDB vs. Vitess

System Properties Comparison JanusGraph vs. OpenQM vs. OrigoDB vs. Vitess

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

QpenQM is a high-performance, self-tuning, multi-value DBMS

A fully ACID in-memory object graph database

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Graph DBMS

Multivalue DBMS

Document store
Object oriented DBMS

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	2.02
Rank	#125	Overall
	#12	Graph DBMS

Score	0.34
Rank	#284	Overall
	#10	Multivalue DBMS

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

Score	0.88
Rank	#203	Overall
	#95	Relational DBMS

Website

janusgraph.org

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-open-qm

origodb.com

vitess.io

Technical documentation

docs.janusgraph.org

origodb.com/docs

vitess.io/docs

Developer

Linux Foundation; originally developed as Titan by Aurelius

Rocket Software, originally Martin Phillips

Robert Friberg et al

The Linux Foundation, PlanetScale

Initial release

2017

1993

2009

under the name LiveDB

2013

Current release

0.6.3, February 2023

3.4-12

15.0.2, December 2022

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

GPLv2, extended commercial license available

Open Source

Apache Version 2.0, commercial licenses available

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

Linux
OS X
Unix
Windows

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

Linux
Windows

Docker
Linux
macOS

Data scheme

yes

with some exceptions

yes

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

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.

yes

can be achieved using .NET

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

APIs and other access methods

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

.NET Client API
HTTP API
LINQ

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

Clojure
Java
Python

.Net
Basic
C
Java
Objective C
PHP
Python

.Net

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

yes

proprietary syntax

Triggers

yes

Domain Events

yes

Partitioning methods

Methods for storing different data on different nodes

yes

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

yes

horizontal partitioning

client side managed; servers are not synchronized

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

Multi-source replication
Source-replica replication

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

Immediate Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

Relationships in graphs

depending on model

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

Durability

Support for making data persistent

yes

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

yes

Write ahead log

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

User authentification and security via Rexster Graph Server

Access rights can be defined down to the item level

Role based authorization

Users with fine-grained authorization concept

no user groups or roles

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

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

Compose for JanusGraph arrives on Bluemix
15 September 2017, ibm.com

provided by Google News

PlanetScale Unveils Distributed MySQL Database Service Based on Vitess
18 May 2021, Datanami

PlanetScale grabs YouTube-developed open-source tech, promises Vitess DBaaS with on-the-fly schema changes
18 May 2021, The Register

They scaled YouTube -- now they’ll shard everyone with PlanetScale
13 December 2018, TechCrunch

With Vitess 4.0, database vendor matures cloud-native platform
13 November 2019, TechTarget

PlanetScale Serves up Vitess-Powered Serverless MySQL
23 November 2021, The New Stack

provided by Google News

Share this page