DBMS > DuckDB vs. MongoDB vs. Rockset

System Properties Comparison DuckDB vs. MongoDB 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

One of the most popular document stores available both as a fully managed cloud service and for deployment on self-managed infrastructure

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

Primary database model

Relational DBMS

Document store

Secondary database models

Spatial DBMS
Search engine

integrated Lucene index, currently in MongoDB Atlas only.
Time Series DBMS

Time Series Collections introduced in Release 5.0
Vector DBMS

currently available in the MongoDB Atlas cloud service only

Relational DBMS
Search engine

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

Score	7.44
Rank	#44	Overall
	#27	Relational DBMS

Score	402.51
Rank	#5	Overall
	#1	Document stores

Score	0.88
Rank	#200	Overall
	#34	Document stores

Website

duckdb.org

www.mongodb.com

rockset.com

Technical documentation

duckdb.org/docs

www.mongodb.com/docs/manual

docs.rockset.com

Developer

MongoDB, Inc

Rockset

Initial release

2018

2009

2019

Current release

1.0.0, June 2024

7.0.5, January 2024

License

Commercial or Open Source

Open Source

MIT License

Open Source

MongoDB Inc.'s Server Side Public License v1. Prior versions were published under GNU AGPL v3.0. Commercial licenses are also available.

commercial

Cloud-based only

Only available as a cloud service

MongoDB available as DBaaS (MongoDB Atlas)

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C++

Server operating systems

server-less

Linux
OS X
Solaris
Windows

hosted

Data scheme

yes

schema-free

Although schema-free, documents of the same collection often follow the same structure. Optionally impose all or part of a schema by defining a JSON schema.

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, decimal, boolean, date, object_id, geospatial

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.

ingestion from XML files supported

Secondary indexes

yes

all fields are automatically indexed

SQL

Support of SQL

yes

Read-only SQL queries via the MongoDB Atlas SQL Interface

Read-only SQL queries, including JOINs

APIs and other access methods

Arrow Database Connectivity (ADBC)
CLI Client
JDBC
ODBC

GraphQL
HTTP REST
Prisma
proprietary protocol using JSON

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

Actionscript

unofficial driver
C
C#
C++
Clojure

unofficial driver
ColdFusion

unofficial driver
D

unofficial driver
Dart

unofficial driver
Delphi

unofficial driver
Erlang
Go
Groovy

unofficial driver
Haskell
Java
JavaScript
Kotlin
Lisp

unofficial driver
Lua

unofficial driver
MatLab

unofficial driver
Perl
PHP
PowerShell

unofficial driver
Prolog

unofficial driver
Python
R

unofficial driver
Ruby
Rust
Scala
Smalltalk

unofficial driver
Swift

Go
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

JavaScript

Triggers

yes

in MongoDB Atlas only

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Partitioned by hashed, ranged, or zoned sharding keys. Live resharding allows users to change their shard keys as an online operation with zero downtime.

Automatic sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-Source deployments with MongoDB Atlas Global Clusters
Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

can be individually decided for each read operation
Immediate Consistency

default behaviour

Eventual Consistency

Foreign keys

Referential integrity

typically not used, however similar functionality with DBRef possible

Transaction concepts

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

ACID

Multi-document ACID Transactions with snapshot isolation

Concurrency

Support for concurrent manipulation of data

yes, multi-version concurrency control (MVCC)

yes

Durability

Support for making data persistent

yes

optional, enabled by default

yes

In-memory capabilities

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

yes

In-memory storage engine introduced with MongoDB version 3.2

User concepts

Access control

Access rights for users and roles

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.