DBMS > Amazon DynamoDB vs. Hazelcast vs. Realm vs. RocksDB vs. Splice Machine

System Properties Comparison Amazon DynamoDB vs. Hazelcast vs. Realm vs. RocksDB vs. Splice Machine

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

A DBMS built for use on mobile devices that’s a fast, easy to use alternative to SQLite and Core Data

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Open-Source SQL RDBMS for Operational and Analytical use cases with native Machine Learning, powered by Hadoop and Spark

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

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

Score	7.41
Rank	#52	Overall
	#8	Document stores

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Score	0.54
Rank	#252	Overall
	#115	Relational DBMS

Website

aws.amazon.com/dynamodb

Technical documentation

docs.aws.amazon.com/dynamodb

hazelcast.org/imdg/docs

realm.io/docs

github.com/facebook/rocksdb/wiki

splicemachine.com/how-it-works

Developer

Amazon

Hazelcast

Realm, acquired by MongoDB in May 2019

Facebook, Inc.

Splice Machine

Initial release

2012

2008

2014

2013

2014

Current release

5.3.6, November 2023

9.2.1, May 2024

3.1, March 2021

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

BSD

Open Source

AGPL 3.0, commercial license available

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

Java

Server operating systems

hosted

All OS with a Java VM

Android
Backend: server-less
iOS
Windows

Linux

Linux
OS X
Solaris
Windows

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

SQL

Support of SQL

SQL-like query language

yes

APIs and other access methods

RESTful HTTP API

JCache
JPA
Memcached protocol
RESTful HTTP API

C++ API
Java API

JDBC
Native Spark Datasource
ODBC

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

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

.Net
Java

with Android only
Objective-C
React Native
Swift

C
C++
Go
Java
Perl
Python
Ruby

C#
C++
Java
JavaScript (Node.js)
Python
R
Scala

Server-side scripts

Stored procedures

yes

Event Listeners, Executor Services

runs within the applications so server-side scripts are unnecessary

yes

Java

Triggers

yes

by integration with AWS Lambda

yes

Events

yes

Change Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

horizontal partitioning

Shared Nothhing Auto-Sharding, Columnar Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Replicated Map

none

yes

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

Yes, via Full Spark Integration

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

Immediate Consistency

Foreign keys

Referential integrity

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

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

ACID

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

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

In-Memory realm

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

yes

Access rights for users, groups and roles according to SQL-standard

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.