DBMS > Apache Phoenix vs. Google BigQuery vs. Google Cloud Bigtable vs. GreptimeDB vs. SWC-DB

System Properties Comparison Apache Phoenix vs. Google BigQuery vs. Google Cloud Bigtable vs. GreptimeDB vs. SWC-DB

Editorial information provided by DB-Engines

Name

Description

A scale-out RDBMS with evolutionary schema built on Apache HBase

Large scale data warehouse service with append-only tables

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 Time Series DBMS built for increased scalability, high performance and efficiency

A high performance, scalable Wide Column DBMS

Primary database model

Relational DBMS

Key-value store
Wide column store

Time Series DBMS

Wide column store

Secondary database models

Time Series DBMS

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

Score	1.97
Rank	#126	Overall
	#59	Relational DBMS

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

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

Score	0.06
Rank	#352	Overall
	#33	Time Series DBMS

Score	0.01
Rank	#376	Overall
	#13	Wide column stores

Website

phoenix.apache.org

cloud.google.com/bigquery

cloud.google.com/bigtable

greptime.com

github.com/kashirin-alex/swc-db
www.swcdb.org

Technical documentation

phoenix.apache.org

cloud.google.com/bigquery/docs

cloud.google.com/bigtable/docs

docs.greptime.com

Developer

Apache Software Foundation

Google

Greptime Inc.

Alex Kashirin

Initial release

2014

2010

2015

2022

2020

Current release

5.0-HBase2, July 2018 and 4.15-HBase1, December 2019

0.5, April 2021

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

Apache Version 2.0

Open Source

GPL V3

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

Rust

C++

Server operating systems

Linux
Unix
Windows

hosted

Android
Docker
FreeBSD
Linux
macOS
Windows

Linux

Data scheme

yes

late-bound, schema-on-read capabilities

yes

schema-free

schema-free, schema definition possible

schema-free

Typing

predefined data types such as float or date

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

SQL-like query language

APIs and other access methods

JDBC

RESTful HTTP/JSON API

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

gRPC
HTTP API
JDBC

Proprietary protocol
Thrift

Supported programming languages

C
C#
C++
Go
Groovy
Java
PHP
Python
Scala

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

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

C++
Erlang
Go
Java
JavaScript

C++

Server-side scripts

Stored procedures

user defined functions

in JavaScript

Python

Triggers

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

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

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency

Immediate Consistency

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

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

ACID

Since BigQuery is designed for querying data

Atomic single-row operations

Concurrency

Support for concurrent manipulation of data

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 Control Lists (using HBase ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC, multi-tenancy

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

Simple rights management via user accounts

More information provided by the system vendor

Specific characteristics

GreptimeDB is a SQL & Python-enabled timeseries database system built from scratch...
» more

Competitive advantages

- Inherits advantages of Rust, such as excellent performance, memory safe, resource...
» more

Typical application scenarios

For IoT industries, GreptimeDB can seamless integrate with message queues and other...
» more

Key customers

Greptime's clients span multiple sectors including IoT, connected vehicles, and energy...
» more

Market metrics

GreptimeDB has garnered global recognition by topping GitHub trends following its...
» more

Licensing and pricing models

GreptimeDB: open source, distributed, cloud-native TSDB; supports Hybrid Time-series...
» more

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.