DBMS > Amazon DynamoDB vs. GridGain vs. Hazelcast vs. HugeGraph

System Properties Comparison Amazon DynamoDB vs. GridGain vs. Hazelcast vs. HugeGraph

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

GridGain is an in-memory computing platform, built on Apache Ignite

A widely adopted in-memory data grid

A fast-speed and highly-scalable Graph DBMS

Primary database model

Document store
Key-value store

Key-value store
Relational DBMS

Key-value store

Graph DBMS

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.45
Rank	#17	Overall
	#3	Document stores
	#2	Key-value stores

Score	1.55
Rank	#150	Overall
	#26	Key-value stores
	#70	Relational DBMS

Score	5.46
Rank	#61	Overall
	#7	Key-value stores

Score	0.17
Rank	#335	Overall
	#31	Graph DBMS

Website

aws.amazon.com/dynamodb

www.gridgain.com

hazelcast.com

github.com/hugegraph
hugegraph.apache.org

Technical documentation

docs.aws.amazon.com/dynamodb

www.gridgain.com/docs/index.html

hazelcast.org/imdg/docs

hugegraph.apache.org/docs

Developer

Amazon

GridGain Systems, Inc.

Hazelcast

Baidu

Initial release

2012

2007

2008

2018

Current release

GridGain 8.5.1

5.3.6, November 2023

0.9

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

commercial

Open Source

Apache Version 2; commercial licenses available

Open Source

Apache Version 2.0

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++, .Net

Java

Server operating systems

hosted

Linux
OS X
Solaris
Windows

All OS with a Java VM

Linux
macOS
Unix

Data scheme

schema-free

yes

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

also supports composite index and range index

SQL

Support of SQL

ANSI-99 for query and DML statements, subset of DDL

SQL-like query language

APIs and other access methods

RESTful HTTP API

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

JCache
JPA
Memcached protocol
RESTful HTTP API

Java API
RESTful HTTP API
TinkerPop Gremlin

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

C#
C++
Java
PHP
Python
Ruby
Scala

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

Groovy
Java
Python

Server-side scripts

Stored procedures

yes (compute grid and cache interceptors can be used instead)

yes

Event Listeners, Executor Services

asynchronous Gremlin script jobs

Triggers

yes

by integration with AWS Lambda

yes (cache interceptors and events)

yes

Events

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

depending on used storage backend, e.g. Cassandra and HBase

Replication methods

Methods for redundantly storing data on multiple nodes

yes

yes (replicated cache)

yes

Replicated Map

yes

depending on used storage backend, e.g. Cassandra and HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes (compute grid and hadoop accelerator)

yes

via hugegraph-spark

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

Immediate Consistency

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

Eventual Consistency

Foreign keys

Referential integrity

yes

edges in graph

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

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

User concepts

Access control

Access rights for users and roles can be defined via the AWS Identity and Access Management (IAM)

Security Hooks for custom implementations

Role-based access control

Users, roles and permissions

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.