DBMS > Amazon DynamoDB vs. Heroic vs. JanusGraph vs. OrigoDB

System Properties Comparison Amazon DynamoDB vs. Heroic vs. JanusGraph vs. OrigoDB

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

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

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

Primary database model

Document store
Key-value store

Time Series DBMS

Graph DBMS

Document store
Object oriented DBMS

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

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

Score	0.46
Rank	#265	Overall
	#22	Time Series DBMS

Score	2.02
Rank	#125	Overall
	#12	Graph DBMS

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

Website

aws.amazon.com/dynamodb

github.com/spotify/heroic

janusgraph.org

origodb.com

Technical documentation

docs.aws.amazon.com/dynamodb

spotify.github.io/heroic

docs.janusgraph.org

origodb.com/docs

Developer

Amazon

Spotify

Linux Foundation; originally developed as Titan by Aurelius

Robert Friberg et al

Initial release

2012

2014

2017

2009

under the name LiveDB

Current release

0.6.3, February 2023

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

Apache 2.0

Open Source

Apache 2.0

Open Source

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

Linux
OS X
Unix
Windows

Linux
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

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

via Elasticsearch

yes

SQL

Support of SQL

APIs and other access methods

RESTful HTTP API

HQL (Heroic Query Language, a JSON-based language)
HTTP API

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

.NET Client API
HTTP API
LINQ

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

Clojure
Java
Python

.Net

Server-side scripts

Stored procedures

yes

Triggers

yes

by integration with AWS Lambda

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

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

horizontal partitioning

client side managed; servers are not synchronized

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

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

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

depending on model

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

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

Write ahead log

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

Role based authorization

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.