DBMS > Graph Engine vs. Heroic vs. IBM Cloudant vs. Kingbase vs. Snowflake

System Properties Comparison Graph Engine vs. Heroic vs. IBM Cloudant vs. Kingbase vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

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

Primary database model

Graph DBMS
Key-value store

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.61
Rank	#240	Overall
	#21	Graph DBMS
	#35	Key-value stores

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

Website

www.graphengine.io

github.com/spotify/heroic

www.ibm.com/products/cloudant

www.kingbase.com.cn

www.snowflake.com

Technical documentation

www.graphengine.io/docs/manual

spotify.github.io/heroic

cloud.ibm.com/docs/Cloudant

docs.snowflake.net/manuals/index.html

Developer

Microsoft

Spotify

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

BeiJing KINGBASE Information technologies inc.

Snowflake Computing Inc.

Initial release

2010

2014

2010

1999

2014

Current release

V8.0, August 2021

License

Commercial or Open Source

Open Source

MIT License

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

.NET and C

Java

Erlang

C and Java

Server operating systems

.NET

hosted

Linux
Windows

hosted

Data scheme

yes

schema-free

yes

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

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

RESTful HTTP API

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

Supported programming languages

C#
C++
F#
Visual Basic

C#
Java
JavaScript
Objective-C
PHP
Ruby

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

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

View functions (Map-Reduce) in JavaScript

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

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

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

yes

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

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

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

fine grained access rights according to SQL-standard

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

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.