DBMS > Hive vs. IBM Cloudant vs. Microsoft Azure Cosmos DB vs. PlanetScale vs. TigerGraph

System Properties Comparison Hive vs. IBM Cloudant vs. Microsoft Azure Cosmos DB vs. PlanetScale vs. TigerGraph

Editorial information provided by DB-Engines

Name

Description

data warehouse software for querying and managing large distributed datasets, built on Hadoop

Database as a Service offering based on Apache CouchDB

Globally distributed, horizontally scalable, multi-model database service

Scalable, distributed, serverless MySQL database platform built on top of Vitess

A complete, distributed, parallel graph computing platform supporting web-scale data analytics in real-time

Primary database model

Relational DBMS

Document store

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

Graph DBMS

Secondary database models

Spatial DBMS

Document store
Spatial DBMS

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

Score	62.59
Rank	#18	Overall
	#12	Relational DBMS

Score	2.73
Rank	#108	Overall
	#20	Document stores

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

Score	1.75
Rank	#146	Overall
	#67	Relational DBMS

Score	1.83
Rank	#141	Overall
	#13	Graph DBMS

Website

hive.apache.org

www.ibm.com/products/cloudant

azure.microsoft.com/services/cosmos-db

planetscale.com

www.tigergraph.com

Technical documentation

cwiki.apache.org/confluence/display/Hive/Home

cloud.ibm.com/docs/Cloudant

learn.microsoft.com/azure/cosmos-db

planetscale.com/docs

docs.tigergraph.com

Developer

Apache Software Foundation

initially developed by Facebook

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Microsoft

PlanetScale

Initial release

2012

2010

2014

2020

2017

Current release

3.1.3, April 2022

License

Commercial or Open Source

Open Source

Apache Version 2

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++

Server operating systems

All OS with a Java VM

hosted

Docker
Linux
macOS

Linux

Data scheme

yes

schema-free

yes

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

SQL

Support of SQL

SQL-like DML and DDL statements

SQL-like query language

yes

with proprietary extensions

SQL-like query language (GSQL)

APIs and other access methods

JDBC
ODBC
Thrift

RESTful HTTP/JSON API

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

ADO.NET
JDBC
MySQL protocol
ODBC

GSQL (TigerGraph Query Language)
Kafka
RESTful HTTP/JSON API

Supported programming languages

C++
Java
PHP
Python

C#
Java
JavaScript
Objective-C
PHP
Ruby

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

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

C++
Java

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

View functions (Map-Reduce) in JavaScript

JavaScript

yes

proprietary syntax

yes

Triggers

yes

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication
Source-replica replication

yes

Implicit feature of the cloud service

Multi-source replication
Source-replica replication

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*

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Relationships in graphs

Transaction concepts

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

atomic operations within a document possible

Multi-item ACID transactions with snapshot isolation within a partition

ACID at shard level

ACID

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

yes

table locks or row locks depending on storage engine

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, groups and roles

Access rights for users can be defined per database

Access rights can be defined down to the item level

Users with fine-grained authorization concept

no user groups or roles

Role-based access control

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.