DBMS > Google BigQuery vs. Hive vs. IBM Cloudant vs. KeyDB

System Properties Comparison Google BigQuery vs. Hive vs. IBM Cloudant vs. KeyDB

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

data warehouse software for querying and managing large distributed datasets, built on Hadoop

Database as a Service offering based on Apache CouchDB

An ultra-fast, open source Key-value store fully compatible with Redis API, modules, and protocols

Primary database model

Relational DBMS

Document store

Key-value store

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

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	61.17
Rank	#18	Overall
	#12	Relational DBMS

Score	2.68
Rank	#106	Overall
	#20	Document stores

Score	0.71
Rank	#226	Overall
	#33	Key-value stores

Website

cloud.google.com/bigquery

hive.apache.org

www.ibm.com/products/cloudant

github.com/Snapchat/KeyDB
keydb.dev

Technical documentation

cloud.google.com/bigquery/docs

cwiki.apache.org/confluence/display/Hive/Home

cloud.ibm.com/docs/Cloudant

docs.keydb.dev

Developer

Google

Apache Software Foundation

initially developed by Facebook

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

EQ Alpha Technology Ltd.

Initial release

2010

2012

2010

2019

Current release

3.1.3, April 2022

License

Commercial or Open Source

commercial

Open Source

Apache Version 2

commercial

Open Source

BSD-3

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

Erlang

C++

Server operating systems

hosted

All OS with a Java VM

hosted

Linux

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

partial

Supported data types are strings, hashes, lists, sets and sorted sets, bit arrays, hyperloglogs and geospatial indexes

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

by using the Redis Search module

SQL

Support of SQL

yes

SQL-like DML and DDL statements

APIs and other access methods

RESTful HTTP/JSON API

JDBC
ODBC
Thrift

RESTful HTTP/JSON API

Proprietary protocol

RESP - REdis Serialization Protoco

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C++
Java
PHP
Python

C#
Java
JavaScript
Objective-C
PHP
Ruby

C
C#
C++
Clojure
Crystal
D
Dart
Elixir
Erlang
Fancy
Go
Haskell
Haxe
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Objective-C
OCaml
Pascal
Perl
PHP
Prolog
Pure Data
Python
R
Rebol
Ruby
Rust
Scala
Scheme
Smalltalk
Swift
Tcl
Visual Basic

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

user defined functions and integration of map-reduce

View functions (Map-Reduce) in JavaScript

Lua

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Eventual Consistency
Strong eventual consistency with CRDTs

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

Optimistic locking, atomic execution of commands blocks and scripts

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

yes

Durability

Support for making data persistent

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

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, groups and roles

Access rights for users can be defined per database

simple password-based access control and ACL

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.