DBMS > DuckDB vs. Hazelcast vs. Microsoft Azure Cosmos DB vs. Rockset

System Properties Comparison DuckDB vs. Hazelcast vs. Microsoft Azure Cosmos DB vs. Rockset

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

An embeddable, in-process, column-oriented SQL OLAP RDBMS

A widely adopted in-memory data grid

Globally distributed, horizontally scalable, multi-model database service

A scalable, reliable search and analytics service in the cloud, built on RocksDB

Primary database model

Relational DBMS

Key-value store

Document store
Graph DBMS
Key-value store
Wide column store

Document store

Secondary database models

Document store

JSON support with IMDG 3.12

Spatial DBMS

Relational DBMS
Search engine

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

Score	4.68
Rank	#76	Overall
	#41	Relational DBMS

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

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

Score	0.84
Rank	#209	Overall
	#35	Document stores

Website

duckdb.org

hazelcast.com

azure.microsoft.com/services/cosmos-db

rockset.com

Technical documentation

duckdb.org/docs

hazelcast.org/imdg/docs

learn.microsoft.com/azure/cosmos-db

docs.rockset.com

Developer

Hazelcast

Microsoft

Rockset

Initial release

2018

2008

2014

2019

Current release

0.10, February 2024

5.3.6, November 2023

License

Commercial or Open Source

Open Source

MIT License

Open Source

Apache Version 2; commercial licenses available

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

C++

Java

C++

Server operating systems

server-less

All OS with a Java VM

hosted

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

JSON types

dynamic typing

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

ingestion from XML files supported

Secondary indexes

yes

All properties auto-indexed by default

all fields are automatically indexed

SQL

Support of SQL

yes

SQL-like query language

Read-only SQL queries, including JOINs

APIs and other access methods

Arrow Database Connectivity (ADBC)
CLI Client
JDBC
ODBC

JCache
JPA
Memcached protocol
RESTful HTTP API

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

HTTP REST

Supported programming languages

C
C#

3rd party driver
C++
Crystal

3rd party driver
Go

3rd party driver
Java
Lisp

3rd party driver
Python
R
Ruby

3rd party driver
Rust
Swift
Zig

3rd party driver

.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

Go
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

Event Listeners, Executor Services

JavaScript

Triggers

yes

Events

JavaScript

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Implicit feature of the cloud service

Automatic sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Replicated Map

yes

Implicit feature of the cloud service

yes

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

Eventual Consistency

Foreign keys

Referential integrity

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

Concurrency

Support for concurrent manipulation of data

yes, multi-version concurrency control (MVCC)

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

Role-based access control

Access rights can be defined down to the item level

Access rights for users and organizations can be defined via Rockset console

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.