DBMS > Google BigQuery vs. GridGain vs. IBM Cloudant vs. Oracle Rdb

System Properties Comparison Google BigQuery vs. GridGain vs. IBM Cloudant vs. Oracle Rdb

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

GridGain is an in-memory computing platform, built on Apache Ignite

Database as a Service offering based on Apache CouchDB

Primary database model

Relational DBMS

Key-value store
Relational DBMS

Document store

Relational DBMS

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

Score	61.90
Rank	#19	Overall
	#13	Relational DBMS

Score	1.53
Rank	#155	Overall
	#26	Key-value stores
	#73	Relational DBMS

Score	2.73
Rank	#108	Overall
	#20	Document stores

Score	1.08
Rank	#187	Overall
	#85	Relational DBMS

Website

cloud.google.com/bigquery

www.gridgain.com

www.ibm.com/products/cloudant

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

Technical documentation

cloud.google.com/bigquery/docs

www.gridgain.com/docs/index.html

cloud.ibm.com/docs/Cloudant

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

Developer

Google

GridGain Systems, Inc.

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Oracle, originally developed by Digital Equipment Corporation (DEC)

Initial release

2010

2007

2010

1984

Current release

GridGain 8.5.1

7.4.1.1, 2021

License

Commercial or Open Source

commercial

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++, .Net

Erlang

Server operating systems

hosted

Linux
OS X
Solaris
Windows

hosted

HP Open VMS

Data scheme

yes

schema-free

Flexible Schema (defined schema, partial schema, 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

SQL

Support of SQL

yes

ANSI-99 for query and DML statements, subset of DDL

yes

APIs and other access methods

RESTful HTTP/JSON API

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

RESTful HTTP/JSON API

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C#
C++
Java
PHP
Python
Ruby
Scala

C#
Java
JavaScript
Objective-C
PHP
Ruby

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes (compute grid and cache interceptors can be used instead)

View functions (Map-Reduce) in JavaScript

Triggers

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes (replicated cache)

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

yes

Consistency concepts

Methods to ensure consistency in a distributed system

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

ACID

atomic operations within a document possible

yes, on a single node

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

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

User concepts

Access control

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

Google Cloud Identity & Access Management (IAM)

Security Hooks for custom implementations

Access rights for users can be defined per database

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.