DBMS > BigchainDB vs. Google Cloud Datastore vs. MySQL vs. TDengine

System Properties Comparison BigchainDB vs. Google Cloud Datastore vs. MySQL vs. TDengine

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

BigchainDB is scalable blockchain database offering decentralization, immutability and native assets

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

Widely used open source RDBMS

Time Series DBMS and big data platform

Primary database model

Document store

Relational DBMS

Key/Value like access via memcached API

Time Series DBMS

Secondary database models

Document store
Spatial DBMS

Relational DBMS

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

Score	0.76
Rank	#216	Overall
	#36	Document stores

Score	4.13
Rank	#71	Overall
	#12	Document stores

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	2.48
Rank	#107	Overall
	#9	Time Series DBMS

Website

www.bigchaindb.com

cloud.google.com/datastore

www.mysql.com

github.com/taosdata/TDengine
tdengine.com

Technical documentation

bigchaindb.readthedocs.io/en/latest

cloud.google.com/datastore/docs

dev.mysql.com/doc

docs.tdengine.com

Developer

Google

Oracle

since 2010, originally MySQL AB, then Sun

TDEngine, previously Taos Data

Initial release

2016

2008

1995

2019

Current release

9.0.0, July 2024

3.0, August 2022

License

Commercial or Open Source

Open Source

AGPL v3

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

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

Python

C and C++

Server operating systems

Linux

hosted

FreeBSD
Linux
OS X
Solaris
Windows

Linux
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

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.

yes

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language (GQL)

yes

with proprietary extensions

Standard SQL with extensions for time-series applications

APIs and other access methods

CLI Client
RESTful HTTP API

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

ADO.NET
JDBC
ODBC
Proprietary native API

JDBC
RESTful HTTP API

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

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

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

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

Server-side scripts

Stored procedures

using Google App Engine

yes

proprietary syntax

Triggers

Callbacks using the Google Apps Engine

yes

yes, via alarm monitoring

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication using Paxos

Multi-source replication
Source-replica replication

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

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

Durability

Support for making data persistent

yes,with MongoDB ord RethinkDB

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

yes

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

Users with fine-grained authorization concept

no user groups or roles

yes

More information provided by the system vendor

Specific characteristics

TDengine™ is a time-series database designed to help traditional industries overcome...
» more

Competitive advantages

High Performance at Any Scale: With its distributed scalable architecture that grows...
» more

Typical application scenarios

TDengine is purpose-built for Industry 4.0 and the Industrial IoT (IIoT) and particularly...
» more

Market metrics

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

Licensing and pricing models

TDengine OSS is free, open-source software released under the AGPLv3. TDengine Enterprise...
» more

News

Optimize Data Consolidation for Multi-Site Renewable Energy Operations
9 September 2024

Connect Power BI to TDengine
6 September 2024

Using Streams and Subscriptions for Alerting
5 September 2024

Solar Panel Monitoring: OPC UA Ingestion
2 September 2024

Time-Series Databases: A Game Changer for the Renewable Energy Industry
30 August 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.