DBMS > Amazon DynamoDB vs. Datomic vs. Hazelcast vs. Postgres-XL

System Properties Comparison Amazon DynamoDB vs. Datomic vs. Hazelcast vs. Postgres-XL

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

Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability

A widely adopted in-memory data grid

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

Primary database model

Document store
Key-value store

Relational DBMS

Key-value store

Relational DBMS

Secondary database models

Document store

JSON support with IMDG 3.12

Document store
Spatial DBMS

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

Score	77.57
Rank	#16	Overall
	#2	Document stores
	#2	Key-value stores

Score	1.76
Rank	#145	Overall
	#66	Relational DBMS

Score	6.87
Rank	#55	Overall
	#6	Key-value stores

Score	0.52
Rank	#256	Overall
	#117	Relational DBMS

Website

aws.amazon.com/dynamodb

www.datomic.com

hazelcast.com

www.postgres-xl.org

Technical documentation

docs.aws.amazon.com/dynamodb

docs.datomic.com

hazelcast.org/imdg/docs

www.postgres-xl.org/documentation

Developer

Amazon

Cognitect

Hazelcast

Initial release

2012

2008

2014

since 2012, originally named StormDB

Current release

1.0.6735, June 2023

5.3.6, November 2023

10 R1, October 2018

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

commercial

limited edition free

Open Source

Apache Version 2; commercial licenses available

Open Source

Mozilla public license

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, Clojure

Java

Server operating systems

hosted

All OS with a Java VM

Linux
macOS

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

yes

XML type, but no XML query functionality

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

yes

distributed, parallel query execution

APIs and other access methods

RESTful HTTP API

JCache
JPA
Memcached protocol
RESTful HTTP API

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

Clojure
Java

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

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

Server-side scripts

Stored procedures

yes

Transaction Functions

yes

Event Listeners, Executor Services

user defined functions

Triggers

yes

by integration with AWS Lambda

By using transaction functions

yes

Events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

But extensive use of caching in the application peers

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

But extensive use of caching in the application peers

yes

Replicated Map

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

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

ACID

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

ACID

MVCC

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

yes

In-memory capabilities

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

yes

recommended only for testing and development

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

fine grained access rights 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.