DBMS > Google BigQuery vs. Google Cloud Datastore vs. IBM Cloudant vs. Ignite vs. Sadas Engine

System Properties Comparison Google BigQuery vs. Google Cloud Datastore vs. IBM Cloudant vs. Ignite vs. Sadas Engine

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service with append-only tables

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

Database as a Service offering based on Apache CouchDB

Apache Ignite is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads, delivering in-memory speeds at petabyte scale.

SADAS Engine is a columnar DBMS specifically designed for high performance in data warehouse environments

Primary database model

Relational DBMS

Document store

Key-value store
Relational DBMS

Relational DBMS

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

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	4.36
Rank	#72	Overall
	#12	Document stores

Score	2.75
Rank	#104	Overall
	#19	Document stores

Score	3.11
Rank	#96	Overall
	#15	Key-value stores
	#49	Relational DBMS

Score	0.07
Rank	#373	Overall
	#157	Relational DBMS

Website

cloud.google.com/bigquery

cloud.google.com/datastore

www.ibm.com/products/cloudant

ignite.apache.org

www.sadasengine.com

Technical documentation

cloud.google.com/bigquery/docs

cloud.google.com/datastore/docs

cloud.ibm.com/docs/Cloudant

apacheignite.readme.io/docs

www.sadasengine.com/en/sadas-engine-download-free-trial-and-documentation/#documentation

Developer

Google

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Apache Software Foundation

SADAS s.r.l.

Initial release

2010

2008

2010

2015

2006

Current release

Apache Ignite 2.6

8.0

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

free trial version available

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

Erlang

C++, Java, .Net

C++

Server operating systems

hosted

Linux
OS X
Solaris
Windows

AIX
Linux
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

yes, details here

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

SQL-like query language (GQL)

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

yes

APIs and other access methods

RESTful HTTP/JSON API

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

RESTful HTTP/JSON API

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

JDBC
ODBC
Proprietary protocol

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

C#
Java
JavaScript
Objective-C
PHP
Ruby

C#
C++
Java
PHP
Python
Ruby
Scala

.Net
C
C#
C++
Groovy
Java
PHP
Python

Server-side scripts

Stored procedures

user defined functions

in JavaScript

using Google App Engine

View functions (Map-Reduce) in JavaScript

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

Triggers

Callbacks using the Google Apps Engine

yes

yes (cache interceptors and events)

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using Paxos

Multi-source replication
Source-replica replication

yes (replicated cache)

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

yes

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

Transaction concepts

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

Since BigQuery is designed for querying data

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

atomic operations within a document possible

ACID

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

managed by 'Learn by Usage'

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, groups and roles based on Google Cloud Identity and Access Management (IAM)

Access rights for users can be defined per database

Security Hooks for custom implementations

Access rights for users, groups and roles according to SQL-standard

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.