DBMS > Google Cloud Bigtable vs. Graphite vs. SAP HANA vs. Vitess

System Properties Comparison Google Cloud Bigtable vs. Graphite vs. SAP HANA vs. Vitess

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 logging and graphing tool for time series data

The storage layer (fixed size database) is called Whisper

In-memory, column based data store. Available as appliance or cloud service

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Key-value store
Wide column store

Time Series DBMS

Relational DBMS

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

Document store
Spatial DBMS

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

Score	3.15
Rank	#95	Overall
	#14	Key-value stores
	#8	Wide column stores

Score	4.83
Rank	#67	Overall
	#4	Time Series DBMS

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Score	0.88
Rank	#203	Overall
	#95	Relational DBMS

Website

cloud.google.com/bigtable

github.com/graphite-project/graphite-web

www.sap.com/products/hana.html

vitess.io

Technical documentation

cloud.google.com/bigtable/docs

graphite.readthedocs.io

help.sap.com/hana

vitess.io/docs

Developer

Google

Chris Davis

SAP

The Linux Foundation, PlanetScale

Initial release

2015

2006

2010

2013

Current release

2.0 SPS07 (April 4, 2023), April 2023

15.0.2, December 2022

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

Open Source

Apache Version 2.0, commercial licenses available

Cloud-based only

Only available as a cloud service

yes

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Python

Server operating systems

hosted

Linux
Unix

Appliance or cloud-service

Docker
Linux
macOS

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

Numeric data only

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

SQL

Support of SQL

yes

with proprietary extensions

APIs and other access methods

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

HTTP API
Sockets

JDBC
ODBC

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

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

JavaScript (Node.js)
Python

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

Server-side scripts

Stored procedures

SQLScript, R

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

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

none

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

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

none

Immediate Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

Atomic single-row operations

ACID

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

locking

yes

table locks or row locks depending on storage engine

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

yes

Users with fine-grained authorization concept

no user groups or roles

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.