DBMS > Google BigQuery vs. IBM Db2 warehouse vs. KeyDB vs. RocksDB vs. SQream DB

System Properties Comparison Google BigQuery vs. IBM Db2 warehouse vs. KeyDB vs. RocksDB vs. SQream DB

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service with append-only tables

Cloud-based data warehousing service

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

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

a GPU-based, columnar RDBMS for big data analytics workloads

Primary database model

Relational DBMS

Key-value store

Relational DBMS

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

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	1.30
Rank	#164	Overall
	#75	Relational DBMS

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

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Score	0.70
Rank	#227	Overall
	#104	Relational DBMS

Website

cloud.google.com/bigquery

www.ibm.com/products/db2/warehouse

github.com/Snapchat/KeyDB
keydb.dev

rocksdb.org

sqream.com

Technical documentation

cloud.google.com/bigquery/docs

docs.keydb.dev

github.com/facebook/rocksdb/wiki

docs.sqream.com

Developer

Google

IBM

EQ Alpha Technology Ltd.

Facebook, Inc.

SQream Technologies

Initial release

2010

2014

2019

2013

2017

Current release

8.11.4, April 2024

2022.1.6, December 2022

License

Commercial or Open Source

commercial

Open Source

BSD-3

Open Source

BSD

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

C++

C++, CUDA, Haskell, Java, Scala

Server operating systems

hosted

Linux

Data scheme

yes

schema-free

yes

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

yes, ANSI Standard SQL Types

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.

Import/export of XML data possible

Secondary indexes

yes

by using the Redis Search module

SQL

Support of SQL

yes

APIs and other access methods

RESTful HTTP/JSON API

.NET Client API
JDBC
ODBC
OLE DB

Proprietary protocol

RESP - REdis Serialization Protoco

C++ API
Java API

.Net
JDBC
ODBC

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

Java
JavaScript (Node.js)
Perl
PHP
Python
R
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

C
C++
Go
Java
Perl
Python
Ruby

C++
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

in JavaScript

PL/SQL, SQL PL

Lua

user defined functions in Python

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning

horizontal and vertical partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Strong eventual consistency with CRDTs

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Since BigQuery is designed for querying data

ACID

Optimistic locking, atomic execution of commands blocks and scripts

yes

ACID

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

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)

fine grained access rights according to SQL-standard

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.