DBMS > Google BigQuery vs. IBM Cloudant vs. LevelDB vs. Quasardb

System Properties Comparison Google BigQuery vs. IBM Cloudant vs. LevelDB vs. Quasardb

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

Database as a Service offering based on Apache CouchDB

Embeddable fast key-value storage library that provides an ordered mapping from string keys to string values

Distributed, high-performance timeseries database

Primary database model

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

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	2.75
Rank	#104	Overall
	#19	Document stores

Score	2.25
Rank	#115	Overall
	#19	Key-value stores

Score	0.21
Rank	#322	Overall
	#29	Time Series DBMS

Website

cloud.google.com/bigquery

www.ibm.com/products/cloudant

github.com/google/leveldb

quasar.ai

Technical documentation

cloud.google.com/bigquery/docs

cloud.ibm.com/docs/Cloudant

github.com/google/leveldb/blob/main/doc/index.md

doc.quasar.ai/master

Developer

Google

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Google

quasardb

Initial release

2010

2011

2009

Current release

1.23, February 2021

3.14.1, January 2024

License

Commercial or Open Source

commercial

Open Source

BSD

commercial

Free community edition, Non-profit organizations and non-commercial usage are eligible for free licenses

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++

Server operating systems

hosted

Illumos
Linux
OS X
Windows

BSD
Linux
OS X
Windows

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

integer and binary

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

with tags

SQL

Support of SQL

yes

SQL-like query language

APIs and other access methods

RESTful HTTP/JSON API

HTTP API

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C#
Java
JavaScript
Objective-C
PHP
Ruby

C++
Go
Java

3rd party binding
JavaScript (Node.js)

3rd party binding
Python

3rd party binding

.Net
C
C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
R

Server-side scripts

Stored procedures

user defined functions

in JavaScript

View functions (Map-Reduce) in JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Sharding

consistent hashing

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

none

Source-replica replication with selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate 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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

yes

Durability

Support for making data persistent

yes

with automatic compression on writes

yes

by using LevelDB

In-memory capabilities

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

yes

Transient mode

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

Cryptographically strong user authentication and audit trail

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.