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

System Properties Comparison Google BigQuery vs. MySQL vs. Oracle 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

Widely used open source RDBMS

Widely used RDBMS

Distributed, fault tolerant key-value store

Primary database model

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Key-value store

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

Secondary database models

Document store
Spatial DBMS

Document store
Graph DBMS

with Oracle Spatial and Graph
RDF store

with Oracle Spatial and Graph
Spatial DBMS

with Oracle Spatial and Graph
Vector DBMS

since Oracle 23

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

Score	61.90
Rank	#19	Overall
	#13	Relational DBMS

Score	1087.72
Rank	#2	Overall
	#2	Relational DBMS

Score	1234.27
Rank	#1	Overall
	#1	Relational DBMS

Score	4.44
Rank	#80	Overall
	#9	Key-value stores

Website

cloud.google.com/bigquery

www.mysql.com

www.oracle.com/database

Technical documentation

cloud.google.com/bigquery/docs

dev.mysql.com/doc

docs.oracle.com/en/database

www.tiot.jp/riak-docs/riak/kv/latest

Developer

Google

Oracle

since 2010, originally MySQL AB, then Sun

Oracle

OpenSource, formerly Basho Technologies

Initial release

2010

1995

1980

2009

Current release

8.3.0, January 2024

23c, September 2023

3.2.0, December 2022

License

Commercial or Open Source

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

restricted free version is available

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

C and C++

Erlang

Server operating systems

hosted

FreeBSD
Linux
OS X
Solaris
Windows

AIX
HP-UX
Linux
OS X
Solaris
Windows
z/OS

Linux
OS X

Data scheme

yes

Schemaless in JSON and XML columns

schema-free

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.

yes

Secondary indexes

yes

restricted

SQL

Support of SQL

yes

with proprietary extensions

yes

with proprietary extensions

APIs and other access methods

RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC
Proprietary native API

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

HTTP API
Native Erlang Interface

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

C
C#
C++
Clojure
Cobol
Delphi
Eiffel
Erlang
Fortran
Groovy
Haskell
Java
JavaScript
Lisp
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Scala
Tcl
Visual Basic

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

yes

proprietary syntax

PL/SQL

also stored procedures in Java possible

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding, horizontal partitioning

Sharding

no "single point of failure"

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

can be realized in PL/SQL

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

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

ACID

not for MyISAM storage engine

ACID

isolation level can be parameterized

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

Version 12c introduced the new option 'Oracle Database In-Memory'

User concepts

Access control

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

Google Cloud Identity & Access Management (IAM)

Users with fine-grained authorization concept

no user groups or roles

fine grained access rights according to SQL-standard

yes, using Riak Security

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.