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

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

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Hypertable has stopped its further development with March 2016 and is removed from the DB-Engines ranking.

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.

An open source BigTable implementation based on distributed file systems such as 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

Wide column store

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

azure.microsoft.com/services/cosmos-db

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

Technical documentation

cloud.google.com/bigtable/docs

learn.microsoft.com/azure/cosmos-db

Developer

Google

Hypertable Inc.

Microsoft

Initial release

2015

2009

2014

2009

Current release

0.9.8.11, March 2016

License

Commercial or Open Source

commercial

Open Source

GNU version 3. Commercial license available

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

C++

Java

Server operating systems

hosted

Linux
OS X
Windows

an inofficial Windows port is available

hosted

Data scheme

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

restricted

only exact value or prefix value scans

yes

All properties auto-indexed by default

SQL

Support of SQL

SQL-like query language

APIs and other access methods

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

C++ API
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
Perl
PHP
Python
Ruby

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

Groovy
Java

Server-side scripts

Stored procedures

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 on file system level

yes

Implicit feature of the cloud service

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

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)

Immediate 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 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.