DBMS > Google BigQuery vs. Graph Engine vs. IBM Cloudant

System Properties Comparison Google BigQuery vs. Graph Engine vs. IBM Cloudant

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 distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

Database as a Service offering based on Apache CouchDB

Primary database model

Relational DBMS

Graph DBMS
Key-value store

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.61
Rank	#240	Overall
	#21	Graph DBMS
	#35	Key-value stores

Score	2.68
Rank	#106	Overall
	#20	Document stores

Website

cloud.google.com/bigquery

www.graphengine.io

www.ibm.com/products/cloudant

Technical documentation

cloud.google.com/bigquery/docs

www.graphengine.io/docs/manual

cloud.ibm.com/docs/Cloudant

Developer

Google

Microsoft

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Initial release

2010

License

Commercial or Open Source

commercial

Open Source

MIT License

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

.NET and C

Erlang

Server operating systems

hosted

.NET

hosted

Data scheme

yes

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

APIs and other access methods

RESTful HTTP/JSON API

RESTful HTTP API

RESTful HTTP/JSON API

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C#
C++
F#
Visual Basic

C#
Java
JavaScript
Objective-C
PHP
Ruby

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

View functions (Map-Reduce) in JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source 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

Foreign keys

Referential integrity

Transaction concepts

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

Since BigQuery is designed for querying data

atomic operations within a document possible

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

Durability

Support for making data persistent

yes

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

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)

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.