DBMS > FatDB vs. Google BigQuery vs. JaguarDB vs. Microsoft Azure Table Storage vs. TDengine

System Properties Comparison FatDB vs. Google BigQuery vs. JaguarDB vs. Microsoft Azure Table Storage vs. TDengine

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

Description

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

Large scale data warehouse service with append-only tables

Performant, highly scalable DBMS for AI and IoT applications

A Wide Column Store for rapid development using massive semi-structured datasets

Time Series DBMS and big data platform

Primary database model

Document store
Key-value store

Relational DBMS

Key-value store
Vector DBMS

Wide column 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	0.00
Rank	#383	Overall
	#60	Key-value stores
	#13	Vector DBMS

Score	4.48
Rank	#75	Overall
	#6	Wide column stores

Score	2.60
Rank	#107	Overall
	#8	Time Series DBMS

Website

cloud.google.com/bigquery

www.jaguardb.com

azure.microsoft.com/en-us/services/storage/tables

github.com/taosdata/TDengine
tdengine.com

Technical documentation

cloud.google.com/bigquery/docs

www.jaguardb.com/support.html

docs.tdengine.com

Developer

FatCloud

Google

DataJaguar, Inc.

Microsoft

TDEngine, previously Taos Data

Initial release

2012

2010

2015

2012

2019

Current release

3.3 July 2023

3.0, August 2022

License

Commercial or Open Source

commercial

Open Source

GPL V3.0

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

C++

the server part. Clients available in other languages

Server operating systems

Windows

hosted

Linux

hosted

Linux
Windows

Data scheme

schema-free

yes

schema-free

yes

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

Via inetgration in SQL Server

yes

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

Standard SQL with extensions for time-series applications

APIs and other access methods

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

RESTful HTTP/JSON API

JDBC
ODBC

RESTful HTTP API

JDBC
RESTful HTTP API

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Scala

.Net
C#
C++
Java
JavaScript (Node.js)
PHP
Python
Ruby

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

Server-side scripts

Stored procedures

yes

via applications

user defined functions

in JavaScript

Triggers

yes

via applications

yes, via alarm monitoring

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Implicit feature of the cloud service

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication

yes

implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

Since BigQuery is designed for querying data

optimistic locking

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

Can implement custom security layer via applications

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

Google Cloud Identity & Access Management (IAM)

rights management via user accounts

Access rights based on private key authentication or shared access signatures

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

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

Why We Need the Next Generation Data Historian
15 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.