DBMS > Amazon DynamoDB vs. Ehcache vs. JanusGraph vs. OpenQM

System Properties Comparison Amazon DynamoDB vs. Ehcache vs. JanusGraph vs. OpenQM

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Hosted, scalable database service by Amazon with the data stored in Amazons cloud

A widely adopted Java cache with tiered storage options

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

Primary database model

Document store
Key-value store

Key-value store

Graph DBMS

Multivalue DBMS

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

Score	70.06
Rank	#17	Overall
	#3	Document stores
	#2	Key-value stores

Score	4.79
Rank	#66	Overall
	#8	Key-value stores

Score	1.85
Rank	#134	Overall
	#12	Graph DBMS

Score	0.28
Rank	#291	Overall
	#10	Multivalue DBMS

Website

aws.amazon.com/dynamodb

www.ehcache.org

janusgraph.org

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

Technical documentation

docs.aws.amazon.com/dynamodb

www.ehcache.org/documentation

docs.janusgraph.org

Developer

Amazon

Terracotta Inc, owned by Software AG

Linux Foundation; originally developed as Titan by Aurelius

Rocket Software, originally Martin Phillips

Initial release

2012

2009

2017

1993

Current release

3.10.0, March 2022

1.0.0, October 2023

3.4-12

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

Apache Version 2; commercial licenses available

Open Source

Apache 2.0

Open Source

GPLv2, extended commercial license available

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Java

Server operating systems

hosted

All OS with a Java VM

Linux
OS X
Unix
Windows

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

Data scheme

schema-free

yes

with some exceptions

Typing

predefined data types such as float or date

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

Secondary indexes

yes

SQL

Support of SQL

APIs and other access methods

RESTful HTTP API

JCache

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

Java

Clojure
Java
Python

.Net
Basic
C
Java
Objective C
PHP
Python

Server-side scripts

Stored procedures

yes

Triggers

yes

by integration with AWS Lambda

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

by using Terracotta Server

yes

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

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

by using Terracotta Server

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

via Faunus, a graph analytics engine

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

Tunable Consistency (Strong, Eventual, Weak)

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

Transaction concepts

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

ACID

ACID across one or more tables within a single AWS account and region

yes

supports JTA and can work as an XA resource

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using a tiered cache-storage approach

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 can be defined via the AWS Identity and Access Management (IAM)

User authentification and security via Rexster Graph Server

Access rights can be defined down to the item level

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.