DBMS > Google BigQuery vs. Google Cloud Bigtable vs. Google Cloud Datastore vs. TDengine

System Properties Comparison Google BigQuery vs. Google Cloud Bigtable vs. Google Cloud Datastore vs. TDengine

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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.

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

Time Series DBMS and big data platform

Primary database model

Relational DBMS

Key-value store
Wide column store

Document store

Time Series DBMS

Secondary database models

Relational DBMS

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

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

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

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	2.60
Rank	#107	Overall
	#8	Time Series DBMS

Website

cloud.google.com/bigquery

cloud.google.com/bigtable

cloud.google.com/datastore

github.com/taosdata/TDengine
tdengine.com

Technical documentation

cloud.google.com/bigquery/docs

cloud.google.com/bigtable/docs

cloud.google.com/datastore/docs

docs.tdengine.com

Developer

Google

TDEngine, previously Taos Data

Initial release

2010

2015

2008

2019

Current release

3.0, August 2022

License

Commercial or Open Source

commercial

Open Source

AGPL V3, also commercial editions available

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

Server operating systems

hosted

Linux
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

yes, details here

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 (GQL)

Standard SQL with extensions for time-series applications

APIs and other access methods

RESTful HTTP/JSON API

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

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

JDBC
RESTful HTTP API

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

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

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

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

Server-side scripts

Stored procedures

user defined functions

in JavaScript

using Google App Engine

Triggers

Callbacks using the Google Apps Engine

yes, via alarm monitoring

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

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

Multi-source replication using Paxos

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

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

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

Transaction concepts

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

Since BigQuery is designed for querying data

Atomic single-row operations

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

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.

User concepts

Access control

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)

yes

More information provided by the system vendor

Specific characteristics

TDengine™ is a next generation data historian purpose-built for Industry 4.0 and...
» more

Competitive advantages

High Performance at any Scale: TDengine is purpose-built for handling massive industrial...
» more

Typical application scenarios

TDengine is designed for Industrial IoT scenarios, including: Manufacturing Connected...
» more

Market metrics

TDengine has garnered over 22,500 stars on GitHub and is used in over 50 countries...
» more

Licensing and pricing models

TDengine OSS is an open source, cloud native time series database. It includes built-in...
» more

News

What Is Predictive Maintenance?
17 May 2024

Can Typical Time-Series Databases Replace Data Historians?
8 May 2024

TDengine 3.3.0.0 Release Notes
7 May 2024

How to Unlock Value from Industrial Data with AI and ML Technology
6 May 2024

Compare InfluxDB vs. TDengine
19 April 2024

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.