DBMS > Google BigQuery vs. Google Cloud Bigtable vs. Oracle Coherence vs. TimescaleDB

System Properties Comparison Google BigQuery vs. Google Cloud Bigtable vs. Oracle Coherence vs. TimescaleDB

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.

Oracles in-memory data grid solution

A time series DBMS optimized for fast ingest and complex queries, based on PostgreSQL

Primary database model

Relational DBMS

Key-value store
Wide column store

Key-value store

Time Series DBMS

Secondary database models

Relational DBMS

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

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	3.15
Rank	#95	Overall
	#14	Key-value stores
	#8	Wide column stores

Score	1.97
Rank	#129	Overall
	#22	Key-value stores

Score	4.46
Rank	#71	Overall
	#5	Time Series DBMS

Website

cloud.google.com/bigquery

cloud.google.com/bigtable

www.oracle.com/java/coherence

www.timescale.com

Technical documentation

cloud.google.com/bigquery/docs

cloud.google.com/bigtable/docs

docs.oracle.com/en/middleware/standalone/coherence

docs.timescale.com

Developer

Google

Oracle

Timescale

Initial release

2010

2015

2007

2017

Current release

14.1, August 2023

2.15.0, May 2024

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

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

Server operating systems

hosted

All OS with a Java VM

Linux
OS X
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

numerics, strings, booleans, arrays, JSON blobs, geospatial dimensions, currencies, binary data, other complex data types

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

yes

full PostgreSQL SQL syntax

APIs and other access methods

RESTful HTTP/JSON API

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

JCache
JPA
RESTful HTTP API

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

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

.Net
C++
Java

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

user defined functions

in JavaScript

user defined functions, PL/pgSQL, PL/Tcl, PL/Perl, PL/Python, PL/Java, PL/PHP, PL/R, PL/Ruby, PL/Scheme, PL/Unix shell

Triggers

yes

Live Events

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

yes, across time and space (hash partitioning) attributes

Replication methods

Methods for redundantly storing data on multiple nodes

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

yes, with selectable consistency level

Source-replica replication with hot standby and reads on replicas

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

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)

Eventual Consistency
Immediate Consistency

Immediate Consistency

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

Atomic single-row operations

configurable

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

optionally

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)

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

authentification to access the cache via certificates or http basic authentication

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.