DBMS > Apache Pinot vs. Databend vs. Microsoft Azure Cosmos DB vs. TerarkDB

System Properties Comparison Apache Pinot vs. Databend vs. Microsoft Azure Cosmos DB vs. TerarkDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Realtime distributed OLAP datastore, designed to answer OLAP queries with low latency

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

Globally distributed, horizontally scalable, multi-model database service

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

Primary database model

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Key-value store

Secondary database models

Spatial DBMS

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

Score	0.40
Rank	#270	Overall
	#125	Relational DBMS

Score	0.30
Rank	#287	Overall
	#130	Relational DBMS

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
	#60	Key-value stores

Website

pinot.apache.org

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

azure.microsoft.com/services/cosmos-db

github.com/bytedance/terarkdb

Technical documentation

docs.pinot.apache.org

docs.databend.com

learn.microsoft.com/azure/cosmos-db

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

Apache Software Foundation and contributors

Databend Labs

Microsoft

ByteDance, originally Terark

Initial release

2015

2021

2014

2016

Current release

1.0.0, September 2023

1.0.59, April 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache Version 2.0

commercial

restricted open source version available

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

Rust

C++

Server operating systems

All OS with a Java JDK11 or higher

hosted
Linux
macOS

hosted

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

JSON types

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

SQL-like query language

yes

SQL-like query language

APIs and other access methods

JDBC

CLI Client
JDBC
RESTful HTTP API

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

C++ API
Java API

Supported programming languages

Go
Java
Python

Go
Java
JavaScript (Node.js)
Python
Rust

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

C++
Java

Server-side scripts

Stored procedures

JavaScript

Triggers

JavaScript

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

none

Sharding

Implicit feature of the cloud service

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

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

Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session 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

In-memory capabilities

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

yes

User concepts

Access control

Users with fine-grained authorization concept, user roles

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.