DBMS > Google BigQuery vs. IBM Db2 Event Store vs. Oracle Rdb vs. Percona Server for MongoDB

System Properties Comparison Google BigQuery vs. IBM Db2 Event Store vs. Oracle Rdb vs. Percona Server for MongoDB

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

Distributed Event Store optimized for Internet of Things use cases

A drop-in replacement for MongoDB Community Edition with enterprise-grade features.

Primary database model

Relational DBMS

Event Store
Time Series DBMS

Relational DBMS

Document store

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

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	0.19
Rank	#323	Overall
	#2	Event Stores
	#28	Time Series DBMS

Score	1.08
Rank	#184	Overall
	#85	Relational DBMS

Score	0.52
Rank	#254	Overall
	#39	Document stores

Website

cloud.google.com/bigquery

www.ibm.com/products/db2-event-store

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

www.percona.com/mongodb/software/percona-server-for-mongodb

Technical documentation

cloud.google.com/bigquery/docs

www.ibm.com/docs/en/db2-event-store

www.oracle.com/database/technologies/related/rdb-doc.html

docs.percona.com/percona-distribution-for-mongodb

Developer

Google

IBM

Oracle, originally developed by Digital Equipment Corporation (DEC)

Percona

Initial release

2010

2017

1984

2015

Current release

2.0

7.4.1.1, 2021

3.4.10-2.10, November 2017

License

Commercial or Open Source

commercial

free developer edition available

commercial

Open Source

GPL Version 2

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

C and C++

C++

Server operating systems

hosted

Linux

Linux, macOS, Windows for the developer addition

HP Open VMS

Linux

Data scheme

yes

Flexible Schema (defined schema, partial schema, schema free)

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.

Secondary indexes

yes

SQL

Support of SQL

yes

through the embedded Spark runtime

yes

APIs and other access methods

RESTful HTTP/JSON API

ADO.NET
DB2 Connect
JDBC
ODBC
RESTful HTTP API

proprietary protocol using JSON

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C
C#
C++
Cobol
Delphi
Fortran
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby
Scala
Visual Basic

Actionscript
C
C#
C++
Clojure
ColdFusion
D
Dart
Delphi
Erlang
Go
Groovy
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Scala
Smalltalk

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

JavaScript

Triggers

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Active-active shard replication

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Eventual 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

yes, on a single node

Concurrency

Support for concurrent manipulation of data

yes

No - written data is immutable

yes

Durability

Support for making data persistent

yes

Yes - Synchronous writes to local disk combined with replication and asynchronous writes in parquet format to permanent shared storage

yes

In-memory capabilities

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

yes

via In-Memory Engine

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

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.