DBMS > Google Cloud Bigtable vs. Graphite vs. Microsoft Azure Cosmos DB vs. VictoriaMetrics

System Properties Comparison Google Cloud Bigtable vs. Graphite vs. Microsoft Azure Cosmos DB vs. VictoriaMetrics

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

Globally distributed, horizontally scalable, multi-model database service

A fast, cost-effective and scalable Time Series DBMS and monitoring solution

Primary database model

Key-value store
Wide column store

Time Series DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Time Series 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	4.57
Rank	#73	Overall
	#5	Time Series DBMS

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

Score	1.32
Rank	#162	Overall
	#14	Time Series DBMS

Website

cloud.google.com/bigtable

github.com/graphite-project/graphite-web

azure.microsoft.com/services/cosmos-db

victoriametrics.com

Technical documentation

cloud.google.com/bigtable/docs

graphite.readthedocs.io

learn.microsoft.com/azure/cosmos-db

docs.victoriametrics.com
github.com/VictoriaMetrics/VictoriaMetrics/wiki

Developer

Google

Chris Davis

Microsoft

VictoriaMetrics

Initial release

2015

2006

2014

2018

Current release

v1.91, May 2023

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

Open Source

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

Python

Server operating systems

hosted

Linux
Unix

hosted

FreeBSD
Linux
macOS
OpenBSD

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

Numeric data only

yes

JSON types

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

APIs and other access methods

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

HTTP API
Sockets

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

Graphite protocol
InfluxDB Line Protocol
OpenTSDB
Prometheus Query API
Prometheus Remote Read/Write

Supported programming languages

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

JavaScript (Node.js)
Python

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

Server-side scripts

Stored procedures

JavaScript

Triggers

JavaScript

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Implicit feature of the cloud service

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

Implicit feature of the cloud service

Synchronous replication

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)

none

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Eventual Consistency

Foreign keys

Referential integrity

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

locking

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.

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.