DBMS > Google BigQuery vs. Hive vs. KeyDB vs. PouchDB

System Properties Comparison Google BigQuery vs. Hive vs. KeyDB vs. PouchDB

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

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

JavaScript DBMS with an API inspired by CouchDB

Primary database model

Relational DBMS

Key-value store

Document store

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

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	59.76
Rank	#18	Overall
	#12	Relational DBMS

Score	0.70
Rank	#229	Overall
	#32	Key-value stores

Score	2.34
Rank	#112	Overall
	#21	Document stores

Website

cloud.google.com/bigquery

hive.apache.org

github.com/Snapchat/KeyDB
keydb.dev

pouchdb.com

Technical documentation

cloud.google.com/bigquery/docs

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

docs.keydb.dev

pouchdb.com/guides

Developer

Google

Apache Software Foundation

initially developed by Facebook

EQ Alpha Technology Ltd.

Apache Software Foundation

Initial release

2010

2012

2019

2012

Current release

3.1.3, April 2022

7.1.1, June 2019

License

Commercial or Open Source

commercial

Open Source

Apache Version 2

Open Source

BSD-3

Open Source

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

JavaScript

Server operating systems

hosted

All OS with a Java VM

Linux

server-less, requires a JavaScript environment (browser, Node.js)

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

yes

via views

SQL

Support of SQL

yes

SQL-like DML and DDL statements

APIs and other access methods

RESTful HTTP/JSON API

JDBC
ODBC
Thrift

Proprietary protocol

RESP - REdis Serialization Protoco

HTTP REST

only for PouchDB Server
JavaScript API

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C++
Java
PHP
Python

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

JavaScript

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

user defined functions and integration of map-reduce

Lua

View functions in JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

with a proxy-based framework, named couchdb-lounge

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication
Source-replica replication

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

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

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

Optimistic locking, atomic execution of commands blocks and scripts

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

yes

by using IndexedDB, WebSQL or LevelDB as backend

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

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.