DBMS > Google Cloud Bigtable vs. Hive vs. Microsoft Azure Cosmos DB vs. TinkerGraph

System Properties Comparison Google Cloud Bigtable vs. Hive vs. Microsoft Azure Cosmos DB vs. TinkerGraph

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Google's NoSQL Big Data database service. It's the same database that powers many core Google services, including Search, Analytics, Maps, and Gmail.

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

Globally distributed, horizontally scalable, multi-model database service

A lightweight, in-memory graph engine that serves as a reference implementation of the TinkerPop3 API

Primary database model

Key-value store
Wide column store

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Graph DBMS

Secondary database models

Spatial DBMS

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

Score	3.26
Rank	#92	Overall
	#13	Key-value stores
	#8	Wide column stores

Score	61.17
Rank	#18	Overall
	#12	Relational DBMS

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

Score	0.08
Rank	#348	Overall
	#35	Graph DBMS

Website

cloud.google.com/bigtable

hive.apache.org

azure.microsoft.com/services/cosmos-db

tinkerpop.apache.org/docs/current/reference/#tinkergraph-gremlin

Technical documentation

cloud.google.com/bigtable/docs

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

learn.microsoft.com/azure/cosmos-db

Developer

Google

Apache Software Foundation

initially developed by Facebook

Microsoft

Initial release

2015

2012

2014

2009

Current release

3.1.3, April 2022

License

Commercial or Open Source

commercial

Open Source

Apache Version 2

commercial

Open Source

Apache 2.0

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

Server operating systems

hosted

All OS with a Java VM

hosted

Data scheme

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

SQL

Support of SQL

SQL-like DML and DDL statements

SQL-like query language

APIs and other access methods

gRPC (using protocol buffers) API
HappyBase (Python library)
HBase compatible API (Java)

JDBC
ODBC
Thrift

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

TinkerPop 3

Supported programming languages

C#
C++
Go
Java
JavaScript (Node.js)
Python

C++
Java
PHP
Python

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

Groovy
Java

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

JavaScript

Triggers

JavaScript

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

none

Replication methods

Methods for redundantly storing data on multiple nodes

Internal replication in Colossus, and regional replication between two clusters in different zones

selectable replication factor

yes

Implicit feature of the cloud service

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate consistency (for a single cluster), Eventual consistency (for two or more replicated clusters)

Eventual Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

none

Foreign keys

Referential integrity

yes

Relationships in graphs

Transaction concepts

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

Atomic single-row operations

Multi-item ACID transactions with snapshot isolation within a partition

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

optional

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 based on Google Cloud Identity and Access Management (IAM)

Access rights for users, groups and roles

Access rights can be defined down to the item level

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.