DBMS > IBM Cloudant vs. Netezza vs. Snowflake vs. Warp 10 vs. YDB

System Properties Comparison IBM Cloudant vs. Netezza vs. Snowflake vs. Warp 10 vs. YDB

Editorial information provided by DB-Engines

Name

Description

Database as a Service offering based on Apache CouchDB

Data warehouse and analytics appliance part of IBM PureSystems

Cloud-based data warehousing service for structured and semi-structured data

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

A distributed fault-tolerant database service, with high availability, scalability, immediate consistency and ACID transactions and providing an Amazon DynamoDB compatible API

Primary database model

Document store

Relational DBMS

Time Series DBMS

Document store
Relational DBMS

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

Score	2.75
Rank	#104	Overall
	#19	Document stores

Score	8.59
Rank	#45	Overall
	#29	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	0.14
Rank	#344	Overall
	#32	Time Series DBMS

Score	0.33
Rank	#287	Overall
	#43	Document stores
	#132	Relational DBMS

Website

www.ibm.com/products/cloudant

www.ibm.com/products/netezza

www.snowflake.com

www.warp10.io

github.com/ydb-platform/ydb
ydb.tech

Technical documentation

cloud.ibm.com/docs/Cloudant

docs.snowflake.net/manuals/index.html

www.warp10.io/content/02_Getting_started

ydb.tech/en/docs

Developer

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

IBM

Snowflake Computing Inc.

SenX

Yandex

Initial release

2010

2000

2014

2015

2019

License

Commercial or Open Source

commercial

Open Source

Apache License 2.0

Open Source

Apache 2.0; commercial license 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

Erlang

Java

Server operating systems

hosted

Linux

included in appliance

hosted

Linux
OS X
Windows

Linux

Data scheme

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

schema-free

Flexible Schema (defined schema, partial schema, schema free)

Typing

predefined data types such as float or date

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like query language (YQL)

APIs and other access methods

RESTful HTTP/JSON API

JDBC
ODBC
OLE DB

CLI Client
JDBC
ODBC

HTTP API
Jupyter
WebSocket

RESTful HTTP API (DynamoDB compatible)

Supported programming languages

C#
Java
JavaScript
Objective-C
PHP
Ruby

C
C++
Fortran
Java
Lua
Perl
Python
R

JavaScript (Node.js)
Python

Go
Java
JavaScript (Node.js)
PHP
Python

Server-side scripts

Stored procedures

View functions (Map-Reduce) in JavaScript

yes

user defined functions

yes

WarpScript

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Sharding

based on HBase

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Source-replica replication

yes

selectable replication factor

based on HBase

Active-passive shard replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

based on HBase

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

atomic operations within a document possible

ACID

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

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

Access rights for users can be defined per database

Users with fine-grained authorization concept

Users with fine-grained authorization concept, user roles and pluggable authentication

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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