DBMS > Google BigQuery vs. Oracle NoSQL vs. Riak KV

System Properties Comparison Google BigQuery vs. Oracle NoSQL vs. Riak KV

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

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, fault tolerant key-value store

Primary database model

Relational DBMS

Document store
Key-value store
Relational DBMS

Key-value store

with links between data sets and object tags for the creation of secondary indexes

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

Score	48.61
Rank	#23	Overall
	#15	Relational DBMS

Score	4.74
Rank	#82	Overall
	#15	Document stores
	#13	Key-value stores
	#44	Relational DBMS

Score	6.63
Rank	#64	Overall
	#8	Key-value stores

Website

cloud.google.com/bigquery

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

riak.com/products/riak-kv

Technical documentation

cloud.google.com/bigquery/docs

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

Developer

Google

Oracle

Basho Technologies

Initial release

2010

2011

2009

Current release

22.1, May 2022

2.1.0, April 2015

License

Commercial or Open Source

commercial

Open Source

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

Open Source

Apache version 2, commercial enterprise edition

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

Erlang

Server operating systems

hosted

Linux
Solaris SPARC/x86

Linux
OS X

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

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

restricted

SQL

Support of SQL

yes

SQL-like DML and DDL statements

APIs and other access methods

RESTful HTTP/JSON API

RESTful HTTP API

HTTP API
Native Erlang Interface

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

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

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

Server-side scripts

Stored procedures

user defined functions

in JavaScript

JavaScript and Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

no "single point of failure"

Replication methods

Methods for redundantly storing data on multiple nodes

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

selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

depending on configuration

Eventual Consistency

Foreign keys

Referential integrity

links between data sets can be stored

Transaction concepts

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

Since BigQuery is designed for querying data

configurable

ACID within a storage node (=shard)

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.

yes

off heap cache

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 and roles

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.