DBMS > CockroachDB vs. EsgynDB vs. Microsoft Azure Cosmos DB vs. Ultipa vs. Yanza

System Properties Comparison CockroachDB vs. EsgynDB vs. Microsoft Azure Cosmos DB vs. Ultipa vs. Yanza

Editorial information provided by DB-Engines

Name

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

Description

CockroachDB is a distributed database architected for modern cloud applications. It is wire compatible with PostgreSQL and backed by a Key-Value Store, which is either RocksDB or a purpose-built derivative, called Pebble.

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

Globally distributed, horizontally scalable, multi-model database service

High performance Graph DBMS supporting HTAP high availability cluster deployment

Time Series DBMS for IoT Applications

Primary database model

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Graph DBMS

Time Series DBMS

Secondary database models

Spatial DBMS

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

Score	4.74
Rank	#67	Overall
	#36	Relational DBMS

Score	0.15
Rank	#325	Overall
	#144	Relational DBMS

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

Score	0.11
Rank	#338	Overall
	#32	Graph DBMS

Website

www.cockroachlabs.com

www.esgyn.cn

azure.microsoft.com/services/cosmos-db

www.ultipa.com

yanza.com

Technical documentation

www.cockroachlabs.com/docs

learn.microsoft.com/azure/cosmos-db

www.ultipa.com/document

Developer

Cockroach Labs

Esgyn

Microsoft

Ultipa

Yanza

Initial release

2015

2014

2019

2015

Current release

24.1.0, May 2024

License

Commercial or Open Source

Open Source

Apache 2.0, commercial license available

commercial

free version available

Cloud-based only

Only available as a cloud service

yes

but mainly used as a service provided by Yanza

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

C++, Java

Server operating systems

Linux
macOS
Windows

Linux

hosted

Windows

Data scheme

dynamic schema

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

yes, wire compatible with PostgreSQL

yes

SQL-like query language

APIs and other access methods

JDBC

ADO.NET
JDBC
ODBC

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

RESTful HTTP API

HTTP API

Supported programming languages

C#
C++
Clojure
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Rust

All languages supporting JDBC/ODBC/ADO.Net

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

C++
Go
Java
JavaScript (Node.js)
Python

any language that supports HTTP calls

Server-side scripts

Stored procedures

Java Stored Procedures

JavaScript

Triggers

JavaScript

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning (by key range)

all tables are translated to an ordered KV store and then broken down into 64MB ranges, which are then used as replicas in RAFT

Sharding

Implicit feature of the cloud service

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using RAFT

Multi-source replication between multi datacenters

yes

Implicit feature of the cloud service

none

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

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

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.

User concepts

Access control

Role-based access control

fine grained access rights according to SQL-standard

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.