DBMS > Amazon DynamoDB vs. BoltDB vs. Heroic vs. JanusGraph vs. TerminusDB

System Properties Comparison Amazon DynamoDB vs. BoltDB vs. Heroic vs. JanusGraph vs. TerminusDB

Editorial information provided by DB-Engines

Name

Description

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

An embedded key-value store for Go.

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

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Primary database model

Document store
Key-value store

Key-value store

Time Series DBMS

Graph DBMS

Secondary database models

Document store
RDF store

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

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

Score	0.74
Rank	#220	Overall
	#31	Key-value stores

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	1.94
Rank	#129	Overall
	#12	Graph DBMS

Score	0.17
Rank	#325	Overall
	#29	Graph DBMS

Website

aws.amazon.com/dynamodb

github.com/boltdb/bolt

github.com/spotify/heroic

janusgraph.org

terminusdb.com

Technical documentation

docs.aws.amazon.com/dynamodb

spotify.github.io/heroic

docs.janusgraph.org

terminusdb.github.io/terminusdb/#

Developer

Amazon

Spotify

Linux Foundation; originally developed as Titan by Aurelius

DataChemist Ltd.

Initial release

2012

2013

2014

2017

2018

Current release

0.6.3, February 2023

11.0.0, January 2023

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

MIT License

Open Source

Apache 2.0

Open Source

Apache 2.0

Open Source

GPL V3

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

Prolog, Rust

Server operating systems

hosted

BSD
Linux
OS X
Solaris
Windows

Linux
OS X
Unix
Windows

Linux

Data scheme

schema-free

yes

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.

Secondary indexes

yes

via Elasticsearch

yes

SQL

Support of SQL

SQL-like query language (WOQL)

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

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

Clojure
Java
Python

JavaScript
Python

Server-side scripts

Stored procedures

yes

Triggers

yes

by integration with AWS Lambda

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

yes

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

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

yes

Journaling Streams

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

none

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

yes

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

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

in-memory journaling

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

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 access control

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.