DBMS > Amazon DocumentDB vs. Hazelcast vs. SQLite vs. SQream DB

System Properties Comparison Amazon DocumentDB vs. Hazelcast vs. SQLite vs. SQream DB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Fast, scalable, highly available, and fully managed MongoDB-compatible database service

A widely adopted in-memory data grid

Widely used embeddable, in-process RDBMS

a GPU-based, columnar RDBMS for big data analytics workloads

Primary database model

Document store

Key-value store

Relational 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	1.91
Rank	#131	Overall
	#24	Document stores

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

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Score	0.74
Rank	#224	Overall
	#103	Relational DBMS

Website

aws.amazon.com/documentdb

hazelcast.com

www.sqlite.org

sqream.com

Technical documentation

aws.amazon.com/documentdb/resources

hazelcast.org/imdg/docs

www.sqlite.org/docs.html

docs.sqream.com

Developer

Hazelcast

Dwayne Richard Hipp

SQream Technologies

Initial release

2019

2008

2000

2017

Current release

5.3.6, November 2023

3.46.0 (23 May 2024), May 2024

2022.1.6, December 2022

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available

Open Source

Public Domain

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++, CUDA, Haskell, Java, Scala

Server operating systems

hosted

All OS with a Java VM

server-less

Linux

Data scheme

schema-free

yes

dynamic column types

yes

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

yes, ANSI Standard SQL 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

SQL

Support of SQL

SQL-like query language

yes

SQL-92 is not fully supported

yes

APIs and other access methods

proprietary protocol using JSON (MongoDB compatible)

JCache
JPA
Memcached protocol
RESTful HTTP API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

.Net
JDBC
ODBC

Supported programming languages

Go
Java
JavaScript (Node.js)
PHP
Python

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

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

C++
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

Event Listeners, Executor Services

user defined functions in Python

Triggers

yes

Events

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

horizontal and vertical partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-availability zones for high availability, asynchronous replication for up to 15 read replicas

yes

Replicated Map

none

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

Immediate Consistency

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

Immediate Consistency

Foreign keys

Referential integrity

typically not used, however similar functionality with DBRef possible

yes

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

Atomic single-document operations

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

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

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.