DBMS > Google BigQuery vs. Ingres vs. OpenTSDB vs. TerarkDB

System Properties Comparison Google BigQuery vs. Ingres vs. OpenTSDB vs. TerarkDB

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

Well established RDBMS

Scalable Time Series DBMS based on HBase

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

Primary database model

Relational DBMS

Time Series DBMS

Key-value store

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

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	4.11
Rank	#81	Overall
	#44	Relational DBMS

Score	1.68
Rank	#146	Overall
	#12	Time Series DBMS

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Website

cloud.google.com/bigquery

www.actian.com/databases/ingres

opentsdb.net

github.com/bytedance/terarkdb

Technical documentation

cloud.google.com/bigquery/docs

docs.actian.com/ingres

opentsdb.net/docs/build/html/index.html

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

Google

Actian Corporation

currently maintained by Yahoo and other contributors

ByteDance, originally Terark

Initial release

2010

1974

originally developed at University Berkely in early 1970s

2011

2016

Current release

11.2, May 2022

License

Commercial or Open Source

commercial

Open Source

LGPL

commercial

restricted open source version 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

Java

C++

Server operating systems

hosted

AIX
HP Open VMS
HP-UX
Linux
Solaris
Windows

Linux
Windows

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

numeric data for metrics, strings for tags

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.

but tools for importing/exporting data from/to XML-files available

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

RESTful HTTP/JSON API

.NET Client API
JDBC
ODBC
proprietary protocol (OpenAPI)

HTTP API
Telnet API

C++ API
Java API

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

Erlang
Go
Java
Python
R
Ruby

C++
Java

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

Ingres Star to access multiple databases simultaneously

Sharding

based on HBase

none

Replication methods

Methods for redundantly storing data on multiple nodes

Ingres Replicator

selectable replication factor

based on HBase

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

based on HBase

Foreign keys

Referential integrity

yes

Transaction concepts

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

Since BigQuery is designed for querying data

ACID

Concurrency

Support for concurrent manipulation of data

yes

MVCC

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 privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

fine grained access rights according to SQL-standard

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.