DBMS > JanusGraph vs. PouchDB vs. SAP HANA vs. STSdb vs. TimesTen

System Properties Comparison JanusGraph vs. PouchDB vs. SAP HANA vs. STSdb vs. TimesTen

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

JavaScript DBMS with an API inspired by CouchDB

In-memory, column based data store. Available as appliance or cloud service

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

In-Memory RDBMS compatible to Oracle

Primary database model

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	2.02
Rank	#125	Overall
	#12	Graph DBMS

Score	2.34
Rank	#112	Overall
	#21	Document stores

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Score	0.10
Rank	#357	Overall
	#51	Key-value stores

Score	1.36
Rank	#161	Overall
	#75	Relational DBMS

Website

janusgraph.org

pouchdb.com

www.sap.com/products/hana.html

github.com/STSSoft/STSdb4

www.oracle.com/database/technologies/related/timesten.html

Technical documentation

docs.janusgraph.org

pouchdb.com/guides

help.sap.com/hana

docs.oracle.com/database/timesten-18.1

Developer

Linux Foundation; originally developed as Titan by Aurelius

Apache Software Foundation

SAP

STS Soft SC

Oracle, TimesTen Performance Software, HP

originally founded in HP Labs it was acquired by Oracle in 2005

Initial release

2017

2012

2010

2011

1998

Current release

0.6.3, February 2023

7.1.1, June 2019

2.0 SPS07 (April 4, 2023), April 2023

4.0.8, September 2015

11 Release 2 (11.2.2.8.0)

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

commercial

Open Source

GPLv2, commercial license available

commercial

Cloud-based only

Only available as a cloud service

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Java

JavaScript

Server operating systems

Linux
OS X
Unix
Windows

server-less, requires a JavaScript environment (browser, Node.js)

Appliance or cloud-service

Windows

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

primitive types and user defined types (classes)

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

via views

yes

SQL

Support of SQL

yes

APIs and other access methods

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

HTTP REST

only for PouchDB Server
JavaScript API

JDBC
ODBC

.NET Client API

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Supported programming languages

Clojure
Java
Python

JavaScript

C#
Java

C
C++
Java
PL/SQL

Server-side scripts

Stored procedures

yes

View functions in JavaScript

SQLScript, R

PL/SQL

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

yes

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

Sharding

with a proxy-based framework, named couchdb-lounge

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

yes

none

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Faunus, a graph analytics engine

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Eventual Consistency

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Foreign keys

Referential integrity

yes

Relationships in graphs

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

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

yes

by using IndexedDB, WebSQL or LevelDB as backend

yes

by means of logfiles and checkpoints

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

yes

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.