DBMS > Apache Impala vs. Cachelot.io vs. CockroachDB vs. EsgynDB vs. Microsoft Azure Cosmos DB

System Properties Comparison Apache Impala vs. Cachelot.io vs. CockroachDB vs. EsgynDB vs. Microsoft Azure Cosmos DB

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for Hadoop

In-memory caching system

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

Primary database model

Relational DBMS

Key-value store

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Secondary database models

Document store

Spatial DBMS

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

Score	12.45
Rank	#40	Overall
	#24	Relational DBMS

Score	0.04
Rank	#388	Overall
	#62	Key-value stores

Score	5.73
Rank	#58	Overall
	#34	Relational DBMS

Score	0.25
Rank	#312	Overall
	#138	Relational DBMS

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

Website

impala.apache.org

cachelot.io

www.cockroachlabs.com

www.esgyn.cn

azure.microsoft.com/services/cosmos-db

Technical documentation

impala.apache.org/impala-docs.html

www.cockroachlabs.com/docs

learn.microsoft.com/azure/cosmos-db

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Cockroach Labs

Esgyn

Microsoft

Initial release

2013

2015

2014

Current release

4.1.0, June 2022

24.1.0, May 2024

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

Simplified BSD License

Open Source

Apache 2.0, commercial license available

commercial

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

C++

C++, Java

Server operating systems

Linux

FreeBSD
Linux
OS X

Linux
macOS
Windows

Linux

hosted

Data scheme

yes

schema-free

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

SQL-like DML and DDL statements

yes, wire compatible with PostgreSQL

yes

SQL-like query language

APIs and other access methods

JDBC
ODBC

Memcached protocol

JDBC

ADO.NET
JDBC
ODBC

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

Supported programming languages

All languages supporting JDBC/ODBC

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
OCaml
Perl
PHP
Python
Ruby

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

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

Java Stored Procedures

JavaScript

Triggers

JavaScript

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

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

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

none

Multi-source replication using RAFT

Multi-source replication between multi datacenters

yes

Implicit feature of the cloud service

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

yes

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

none

Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

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

Access rights for users, groups and roles

based on Apache Sentry and Kerberos

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.