DBMS > Databend vs. FatDB vs. Microsoft Azure Cosmos DB vs. ToroDB

System Properties Comparison Databend vs. FatDB vs. Microsoft Azure Cosmos DB vs. ToroDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

ToroDB seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

An open-source, elastic, and workload-aware cloud data warehouse designed to meet businesses' massive-scale analytics needs at low cost and with low complexity

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

Globally distributed, horizontally scalable, multi-model database service

A MongoDB-compatible JSON document store, built on top of PostgreSQL

Primary database model

Relational DBMS

Document store
Key-value store

Document store
Graph DBMS
Key-value store
Wide column store

Document store

Secondary database models

Spatial DBMS

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

Score	0.34
Rank	#283	Overall
	#130	Relational DBMS

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

Website

github.com/datafuselabs/databend
www.databend.com

azure.microsoft.com/services/cosmos-db

github.com/torodb/server

Technical documentation

docs.databend.com

learn.microsoft.com/azure/cosmos-db

Developer

Databend Labs

FatCloud

Microsoft

8Kdata

Initial release

2021

2012

2014

2016

Current release

1.0.59, April 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

AGPL-V3

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

Rust

Java

Server operating systems

hosted
Linux
macOS

Windows

hosted

All OS with a Java 7 VM

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

JSON types

yes

string, integer, double, boolean, date, object_id

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

SQL

Support of SQL

yes

Via inetgration in SQL Server

SQL-like query language

APIs and other access methods

CLI Client
JDBC
RESTful HTTP API

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

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

Supported programming languages

Go
Java
JavaScript (Node.js)
Python
Rust

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

Server-side scripts

Stored procedures

yes

via applications

JavaScript

Triggers

yes

via applications

JavaScript

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Implicit feature of the cloud service

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

selectable replication factor

yes

Implicit feature of the cloud service

Source-replica replication

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

Eventual Consistency
Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

yes

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

User concepts

Access control

Users with fine-grained authorization concept, user roles

Can implement custom security layer via applications

Access rights can be defined down to the item level

Access rights for 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.