DBMS > Amazon DynamoDB vs. BoltDB vs. Hazelcast vs. JanusGraph vs. Microsoft Azure Cosmos DB

System Properties Comparison Amazon DynamoDB vs. BoltDB vs. Hazelcast vs. JanusGraph vs. Microsoft Azure Cosmos DB

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.

A widely adopted in-memory data grid

A Graph DBMS optimized for distributed clusters

It was forked from the latest code base of Titan in January 2017

Globally distributed, horizontally scalable, multi-model database service

Primary database model

Document store
Key-value store

Key-value store

Graph DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Secondary database models

Document store

JSON support with IMDG 3.12

Spatial DBMS

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	5.97
Rank	#57	Overall
	#6	Key-value stores

Score	1.94
Rank	#129	Overall
	#12	Graph DBMS

Score	29.04
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Website

aws.amazon.com/dynamodb

github.com/boltdb/bolt

hazelcast.com

janusgraph.org

azure.microsoft.com/services/cosmos-db

Technical documentation

docs.aws.amazon.com/dynamodb

hazelcast.org/imdg/docs

docs.janusgraph.org

learn.microsoft.com/azure/cosmos-db

Developer

Amazon

Hazelcast

Linux Foundation; originally developed as Titan by Aurelius

Microsoft

Initial release

2012

2013

2008

2017

2014

Current release

5.3.6, November 2023

0.6.3, February 2023

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

MIT License

Open Source

Apache Version 2; commercial licenses available

Open Source

Apache 2.0

commercial

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

BSD
Linux
OS X
Solaris
Windows

All OS with a Java VM

Linux
OS X
Unix
Windows

hosted

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

JSON types

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

the object must implement a serialization strategy

Secondary indexes

yes

All properties auto-indexed by default

SQL

Support of SQL

SQL-like query language

APIs and other access methods

RESTful HTTP API

JCache
JPA
Memcached protocol
RESTful HTTP API

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

.Net
C#
C++
Clojure
Go
Java
JavaScript (Node.js)
Python
Scala

Clojure
Java
Python

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

Server-side scripts

Stored procedures

yes

Event Listeners, Executor Services

yes

JavaScript

Triggers

yes

by integration with AWS Lambda

yes

Events

yes

JavaScript

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)

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

yes

Replicated Map

yes

Implicit feature of the cloud service

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

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

none

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

Eventual Consistency
Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session 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

one or two-phase-commit; repeatable reads; read commited

ACID

Multi-item ACID transactions with snapshot isolation within a partition

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 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)

Role-based access control

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.