DBMS > JanusGraph vs. Machbase Neo vs. OrientDB vs. SQLite vs. Stardog

System Properties Comparison JanusGraph vs. Machbase Neo vs. OrientDB vs. SQLite vs. Stardog

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

TimeSeries DBMS for AIoT and BigData

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

Widely used embeddable, in-process RDBMS

Enterprise Knowledge Graph platform and graph DBMS with high availability, high performance reasoning, and virtualization

Primary database model

Graph DBMS

Time Series DBMS

Document store
Graph DBMS
Key-value store

Relational DBMS

Graph DBMS
RDF store

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

Score	1.94
Rank	#129	Overall
	#12	Graph DBMS

Score	0.12
Rank	#339	Overall
	#30	Time Series DBMS

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

Score	2.02
Rank	#123	Overall
	#11	Graph DBMS
	#6	RDF stores

Website

Technical documentation

docs.janusgraph.org

machbase.com/dbms

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

www.sqlite.org/docs.html

docs.stardog.com

Developer

Linux Foundation; originally developed as Titan by Aurelius

Machbase

OrientDB LTD; CallidusCloud; SAP

Dwayne Richard Hipp

Stardog-Union

Initial release

2017

2013

2010

2000

2010

Current release

0.6.3, February 2023

V8.0, August 2023

3.2.29, March 2024

3.45.3 (15 April 2024), April 2024

7.3.0, May 2020

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

free test version available

Open Source

Apache version 2

Open Source

Public Domain

commercial

60-day fully-featured trial license; 1-year fully-featured non-commercial use license for academics/students

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

Linux
macOS
Windows

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

server-less

Linux
macOS
Windows

Data scheme

yes

schema-free

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

yes

dynamic column types

schema-free and OWL/RDFS-schema support

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.

Import/export of XML data possible

Secondary indexes

yes

supports real-time indexing in full-text and geospatial

SQL

Support of SQL

SQL-like query language

SQL-like query language, no joins

yes

SQL-92 is not fully supported

Yes, compatible with all major SQL variants through dedicated BI/SQL Server

APIs and other access methods

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

gRPC
HTTP REST
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC

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

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

GraphQL query language
HTTP API
Jena RDF API
OWL
RDF4J API
Sesame REST HTTP Protocol
SNARL
SPARQL
Spring Data
Stardog Studio
TinkerPop 3

Supported programming languages

Clojure
Java
Python

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

.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

.Net
Clojure
Groovy
Java
JavaScript
Python
Ruby

Server-side scripts

Stored procedures

yes

Java, Javascript

user defined functions and aggregates, HTTP Server extensions in Java

Triggers

yes

Hooks

yes

via event handlers

Partitioning methods

Methods for storing different data on different nodes

yes

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

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

Multi-source replication

none

Multi-source replication in HA-Cluster

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Faunus, a graph analytics engine

could be achieved with distributed queries

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Immediate Consistency in HA-Cluster

Foreign keys

Referential integrity

yes

Relationships in graphs

yes

relationship in graphs

yes

relationships in graphs

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

volatile and lookup table

yes

User concepts

Access control

User authentification and security via Rexster Graph Server

simple password-based access control

Access rights for users and roles; record level security configurable

Access rights for users and 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.