DBMS > Apache Kylin vs. Microsoft Azure Cosmos DB vs. NuoDB vs. PouchDB

System Properties Comparison Apache Kylin vs. Microsoft Azure Cosmos DB vs. NuoDB vs. PouchDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A distributed analytics engine for big data, providing a SQL interface and multi-dimensional analysis (OLAP) and leveraging the Hadoop stack

Globally distributed, horizontally scalable, multi-model database service

NuoDB is a webscale distributed database that supports SQL and ACID transactions

JavaScript DBMS with an API inspired by CouchDB

Primary database model

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

Document store

Secondary database models

Spatial DBMS

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

Score	1.18
Rank	#172	Overall
	#79	Relational DBMS

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

Score	0.89
Rank	#198	Overall
	#92	Relational DBMS

Score	2.28
Rank	#115	Overall
	#21	Document stores

Website

kylin.apache.org

azure.microsoft.com/services/cosmos-db

www.3ds.com/nuodb-distributed-sql-database

pouchdb.com

Technical documentation

kylin.apache.org/docs

learn.microsoft.com/azure/cosmos-db

doc.nuodb.com

pouchdb.com/guides

Developer

Apache Software Foundation, originally contributed from eBay Inc

Microsoft

Dassault Systèmes

originally NuoDB, Inc.

Apache Software Foundation

Initial release

2015

2014

2013

2012

Current release

3.1.0, July 2020

7.1.1, June 2019

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

limited edition free

Open Source

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

C++

JavaScript

Server operating systems

Linux

hosted

Amazon EC2, Windows Azure, SoftLayer
Linux
OS X
Windows

server-less, requires a JavaScript environment (browser, Node.js)

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

JSON types

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

yes

via views

SQL

Support of SQL

ANSI SQL for queries (using Apache Calcite)

SQL-like query language

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

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

ADO.NET
JDBC
ODBC

HTTP REST

only for PouchDB Server
JavaScript API

Supported programming languages

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

.Net
C
C++
Go
Java
JavaScript
JavaScript (Node.js)
PHP
Python
Ruby

JavaScript

Server-side scripts

Stored procedures

JavaScript

Java, SQL

View functions in JavaScript

Triggers

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

data is dynamically stored/cached on the nodes where it is read/written

Sharding

with a proxy-based framework, named couchdb-lounge

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

yes

Managed transparently by NuoDB

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

yes

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

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Multi-item ACID transactions with snapshot isolation within a partition

ACID

tunable commit protocol

Concurrency

Support for concurrent manipulation of data

yes

MVCC

Durability

Support for making data persistent

yes

by using IndexedDB, WebSQL or LevelDB as backend

In-memory capabilities

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

yes

Temporary table

yes

User concepts

Access control

Access rights can be defined down to the item level

Standard SQL roles/ privileges, Administrative Users

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.