DBMS > 4D vs. Datomic vs. Hazelcast vs. Microsoft Azure Cosmos DB vs. Tarantool

System Properties Comparison 4D vs. Datomic vs. Hazelcast vs. Microsoft Azure Cosmos DB vs. Tarantool

Editorial information provided by DB-Engines

Name

Description

Application development environment with integrated database management system

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

A widely adopted in-memory data grid

Globally distributed, horizontally scalable, multi-model database service

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

Primary database model

Relational DBMS

Key-value store

Document store
Graph DBMS
Key-value store
Wide column store

Document store
Key-value store
Relational DBMS

Secondary database models

Document store

JSON support with IMDG 3.12

Spatial DBMS

with Tarantool/GIS extension

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

Score	2.58
Rank	#108	Overall
	#54	Relational DBMS

Score	1.59
Rank	#150	Overall
	#69	Relational DBMS

Score	5.97
Rank	#57	Overall
	#6	Key-value stores

Score	29.04
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	1.72
Rank	#144	Overall
	#25	Document stores
	#25	Key-value stores
	#66	Relational DBMS

Website

www.4d.com

www.datomic.com

hazelcast.com

azure.microsoft.com/services/cosmos-db

www.tarantool.io

Technical documentation

developer.4d.com

docs.datomic.com

hazelcast.org/imdg/docs

learn.microsoft.com/azure/cosmos-db

www.tarantool.io/en/doc

Developer

4D, Inc

Cognitect

Hazelcast

Microsoft

Initial release

1984

2012

2008

2014

2008

Current release

v20, April 2023

1.0.6735, June 2023

5.3.6, November 2023

2.10.0, May 2022

License

Commercial or Open Source

commercial

limited edition free

Open Source

Apache Version 2; commercial licenses available

commercial

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

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

C and C++

Server operating systems

OS X
Windows

All OS with a Java VM

hosted

BSD
Linux
macOS

Data scheme

yes

schema-free

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

Typing

predefined data types such as float or date

yes

JSON types

string, double, decimal, uuid, integer, blob, boolean, datetime

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

All properties auto-indexed by default

yes

SQL

Support of SQL

yes

close to SQL 92

SQL-like query language

Full-featured ANSI SQL support

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

RESTful HTTP API

JCache
JPA
Memcached protocol
RESTful HTTP API

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

Open binary protocol

Supported programming languages

4D proprietary IDE
PHP

Clojure
Java

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

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

C
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

Server-side scripts

Stored procedures

yes

Transaction Functions

yes

Event Listeners, Executor Services

JavaScript

Lua, C and SQL stored procedures

Triggers

yes

By using transaction functions

yes

Events

JavaScript

yes, before/after data modification events, on replication events, client session events

Partitioning methods

Methods for storing different data on different nodes

none

But extensive use of caching in the application peers

Sharding

Implicit feature of the cloud service

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

none

But extensive use of caching in the application peers

yes

Replicated Map

yes

Implicit feature of the cloud service

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

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

Multi-item ACID transactions with snapshot isolation within a partition

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

Concurrency

Support for concurrent manipulation of data

yes

yes, cooperative multitasking

Durability

Support for making data persistent

yes

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

yes

yes, write ahead logging

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

yes, full featured in-memory storage engine with persistence

User concepts

Access control

Users and groups

Role-based access control

Access rights can be defined down to the item level

Access Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
Users and Roles

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.