DBMS > Microsoft Azure Cosmos DB vs. NSDb vs. ReductStore vs. Spark SQL

System Properties Comparison Microsoft Azure Cosmos DB vs. NSDb vs. ReductStore vs. Spark SQL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Globally distributed, horizontally scalable, multi-model database service

Scalable, High-performance Time Series DBMS designed for Real-time Analytics on top of Kubernetes

Designed to manage unstructured time-series data efficiently, providing unique features such as storing time-stamped blobs with labels, customizable data retention policies, and a straightforward FIFO quota system.

Spark SQL is a component on top of 'Spark Core' for structured data processing

Primary database model

Document store
Graph DBMS
Key-value store
Wide column store

Time Series DBMS

Relational DBMS

Secondary database models

Spatial DBMS

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

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

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

Score	18.96
Rank	#33	Overall
	#20	Relational DBMS

Website

azure.microsoft.com/services/cosmos-db

nsdb.io

github.com/reductstore
www.reduct.store

spark.apache.org/sql

Technical documentation

learn.microsoft.com/azure/cosmos-db

nsdb.io/Architecture

www.reduct.store/docs

spark.apache.org/docs/latest/sql-programming-guide.html

Developer

Microsoft

ReductStore LLC

Apache Software Foundation

Initial release

2014

2017

2023

2014

Current release

1.9, March 2024

3.5.0 ( 2.13), September 2023

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

Open Source

Business Source License 1.1

Open Source

Apache 2.0

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

C++, Rust

Scala

Server operating systems

hosted

Linux
macOS

Docker
Linux
macOS
Windows

Linux
OS X
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

JSON types

yes: int, bigint, decimal, string

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.

Secondary indexes

yes

All properties auto-indexed by default

all fields are automatically indexed

SQL

Support of SQL

SQL-like query language

SQL-like DML and DDL statements

APIs and other access methods

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

gRPC
HTTP REST
WebSocket

HTTP API

JDBC
ODBC

Supported programming languages

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

Java
Scala

C++
JavaScript (Node.js)
Python
Rust

Java
Python
R
Scala

Server-side scripts

Stored procedures

JavaScript

Triggers

JavaScript

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding

yes, utilizing Spark Core

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

none

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

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

Multi-item ACID transactions with snapshot isolation within a partition

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Using Apache Lucene

yes

In-memory capabilities

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

User concepts

Access control

Access rights can be defined down to the item level

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.