DBMS > Google BigQuery vs. OpenTenBase vs. Oracle NoSQL vs. Quasardb

System Properties Comparison Google BigQuery vs. OpenTenBase vs. Oracle NoSQL vs. Quasardb

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

An enterprise-level distributed HTAP open source database based on PostgreSQL

A multi-model, scalable, distributed NoSQL database, designed to provide highly reliable, flexible, and available data management across a configurable set of storage nodes

Distributed, high-performance timeseries database

Primary database model

Relational DBMS

Document store
Key-value store
Relational DBMS

Time Series DBMS

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

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	0.08
Rank	#370	Overall
	#156	Relational DBMS

Score	3.05
Rank	#97	Overall
	#17	Document stores
	#16	Key-value stores
	#50	Relational DBMS

Score	0.21
Rank	#322	Overall
	#29	Time Series DBMS

Website

cloud.google.com/bigquery

github.com/OpenTenBase/OpenTenBase
www.opentenbase.org

www.oracle.com/database/nosql/technologies/nosql

quasar.ai

Technical documentation

cloud.google.com/bigquery/docs

docs.opentenbase.org
docs.opentenbase.org/en

docs.oracle.com/en/database/other-databases/nosql-database/index.html

doc.quasar.ai/master

Developer

Google

OpenAtom Foundation, previously Tencent

Oracle

quasardb

Initial release

2010

2011

2009

Current release

2.5, January 2024

24.1, May 2024

3.14.1, January 2024

License

Commercial or Open Source

commercial

Open Source

BSD-3

Open Source

Proprietary for Enterprise Edition (Oracle Database EE license has Oracle NoSQL database EE covered: details)

commercial

Free community edition, Non-profit organizations and non-commercial usage are eligible for free licenses

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

Linux

Linux
Solaris SPARC/x86

BSD
Linux
OS X
Windows

Data scheme

yes

Support Fixed schema and Schema-less deployment with the ability to interoperate between them.

schema-free

Typing

predefined data types such as float or date

yes

optional

yes

integer and binary

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

with tags

SQL

Support of SQL

yes

SQL-like DML and DDL statements

SQL-like query language

APIs and other access methods

RESTful HTTP/JSON API

RESTful HTTP API

HTTP API

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C
Go
Java
PHP
Python

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

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

Server-side scripts

Stored procedures

user defined functions

in JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

consistent hashing

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Electable source-replica replication per shard. Support distributed global deployment with Multi-region table feature

Source-replica replication with selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

depending on configuration

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

ACID

configurable

ACID within a storage node (=shard)

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

by using LevelDB

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

off heap cache

yes

Transient mode

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 according to SQL-standard

Access rights for users and roles

Cryptographically strong user authentication and audit trail

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.