DBMS > Heroic vs. IBM Cloudant vs. Kingbase vs. Snowflake vs. TDSQL for MySQL

System Properties Comparison Heroic vs. IBM Cloudant vs. Kingbase vs. Snowflake vs. TDSQL for MySQL

Editorial information provided by DB-Engines

Name

Description

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

Database as a Service offering based on Apache CouchDB

An enterprise-class RDBMS compatible with PostgreSQL and Oracle and widely used in China.

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

A high-performance distributed database management system with features such as automatic sharding, intelligent operation and maintenance, elastic scalability without downtime, and enterprise-grade security. It is highly compatible with MySQL.

Primary database model

Time Series DBMS

Document store

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	2.68
Rank	#106	Overall
	#20	Document stores

Score	0.45
Rank	#262	Overall
	#123	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	0.85
Rank	#205	Overall
	#95	Relational DBMS

Website

github.com/spotify/heroic

www.ibm.com/products/cloudant

www.kingbase.com.cn

www.snowflake.com

www.tencentcloud.com/products/dcdb

Technical documentation

spotify.github.io/heroic

cloud.ibm.com/docs/Cloudant

docs.snowflake.net/manuals/index.html

www.tencentcloud.com/document/product/1042

Developer

Spotify

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

BeiJing KINGBASE Information technologies inc.

Snowflake Computing Inc.

Tencent

Initial release

2014

2010

1999

2014

2013

Current release

V8.0, August 2021

License

Commercial or Open Source

Open Source

Apache 2.0

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

Java

Erlang

C and Java

Server operating systems

hosted

Linux
Windows

hosted

Data scheme

schema-free

yes

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

yes

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

via Elasticsearch

yes

SQL

Support of SQL

Standard with numerous extensions

yes

APIs and other access methods

HQL (Heroic Query Language, a JSON-based language)
HTTP API

RESTful HTTP/JSON API

ADO.NET
gokb
JDBC
kdbndp
ODBC
PDI
PDO
Pro*C
psycopg2
QT

CLI Client
JDBC
ODBC

JDBC
ODBC

Supported programming languages

C#
Java
JavaScript
Objective-C
PHP
Ruby

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

JavaScript (Node.js)
Python

C
C#
C++
Java
PHP
Python
Ruby

Server-side scripts

Stored procedures

View functions (Map-Reduce) in JavaScript

user defined functions

yes

Triggers

yes

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning (by range, list and hash) and vertical partitioning

yes

Automatic sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

yes

Multi-source replication
Source-replica 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

Eventual Consistency

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.

User concepts

Access control

Access rights for users can be defined per database

fine grained access rights according to SQL-standard

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

Users with fine-grained authorization concept

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.