DBMS > Amazon DynamoDB vs. Hazelcast vs. Heroic vs. Percona Server for MongoDB vs. TigerGraph

System Properties Comparison Amazon DynamoDB vs. Hazelcast vs. Heroic vs. Percona Server for MongoDB vs. TigerGraph

Editorial information provided by DB-Engines

Name

Description

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

A widely adopted in-memory data grid

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

A drop-in replacement for MongoDB Community Edition with enterprise-grade features.

A complete, distributed, parallel graph computing platform supporting web-scale data analytics in real-time

Primary database model

Document store
Key-value store

Secondary database models

Document store

JSON support with IMDG 3.12

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

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	0.52
Rank	#254	Overall
	#39	Document stores

Score	1.83
Rank	#139	Overall
	#13	Graph DBMS

Website

aws.amazon.com/dynamodb

hazelcast.com

github.com/spotify/heroic

www.percona.com/mongodb/software/percona-server-for-mongodb

www.tigergraph.com

Technical documentation

docs.aws.amazon.com/dynamodb

hazelcast.org/imdg/docs

spotify.github.io/heroic

docs.percona.com/percona-distribution-for-mongodb

docs.tigergraph.com

Developer

Amazon

Hazelcast

Spotify

Percona

Initial release

2012

2008

2014

2015

2017

Current release

5.3.6, November 2023

3.4.10-2.10, November 2017

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

GPL Version 2

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

C++

Server operating systems

hosted

All OS with a Java VM

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.

yes

the object must implement a serialization strategy

Secondary indexes

yes

via Elasticsearch

yes

SQL

Support of SQL

SQL-like query language

SQL-like query language (GSQL)

APIs and other access methods

RESTful HTTP API

JCache
JPA
Memcached protocol
RESTful HTTP API

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

proprietary protocol using JSON

GSQL (TigerGraph Query Language)
Kafka
RESTful HTTP/JSON 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

Actionscript
C
C#
C++
Clojure
ColdFusion
D
Dart
Delphi
Erlang
Go
Groovy
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Scala
Smalltalk

C++
Java

Server-side scripts

Stored procedures

yes

Event Listeners, Executor Services

JavaScript

yes

Triggers

yes

by integration with AWS Lambda

yes

Events

Partitioning methods

Methods for storing different data on different nodes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Replicated Map

yes

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

Eventual 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

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

In-memory capabilities

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

yes

via In-Memory Engine

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

Access rights for users and roles

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.