DBMS > Google BigQuery vs. IBM Db2 vs. Memcached vs. Warp 10

System Properties Comparison Google BigQuery vs. IBM Db2 vs. Memcached vs. Warp 10

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

Common in IBM host environments, 2 different versions for host and Windows/Linux

In-memory key-value store, originally intended for caching

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Primary database model

Relational DBMS

Since Version 10.5 support for JSON/BSON documents compatible with MongoDB

Key-value store

Time Series DBMS

Secondary database models

Document store
RDF store

in Db2 LUW (Linux, Unix, Windows)
Spatial DBMS

with Db2 Spatial Extender

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

Score	61.90
Rank	#19	Overall
	#13	Relational DBMS

Score	127.49
Rank	#8	Overall
	#5	Relational DBMS

Score	20.74
Rank	#32	Overall
	#4	Key-value stores

Score	0.08
Rank	#358	Overall
	#35	Time Series DBMS

Website

cloud.google.com/bigquery

www.ibm.com/products/db2

www.memcached.org

www.warp10.io

Technical documentation

cloud.google.com/bigquery/docs

www.ibm.com/docs/en/db2

github.com/memcached/memcached/wiki

www.warp10.io/content/02_Getting_started

Developer

Google

IBM

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

SenX

Initial release

2010

1983

host version

2003

2015

Current release

12.1, October 2016

1.6.25, March 2024

License

Commercial or Open Source

commercial

free version is available

Open Source

BSD license

Open Source

Apache License 2.0

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

Java

Server operating systems

hosted

AIX
HP-UX
Linux
Solaris
Windows
z/OS

FreeBSD
Linux
OS X
Unix
Windows

Linux
OS X
Windows

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

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.

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

RESTful HTTP/JSON API

ADO.NET
JDBC
JSON style queries

MongoDB compatible
ODBC
XQuery

Proprietary protocol

HTTP API
Jupyter
WebSocket

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C
C#
C++
Cobol
Delphi
Fortran
Java
Perl
PHP
Python
Ruby
Visual Basic

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
Perl
PHP
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

WarpScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

only with Windows/Unix/Linux Version

none

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

yes

with separate tools (MQ, InfoSphere)

none

Repcached, a Memcached patch, provides this functionallity

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

based on HBase

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

Concurrency

Support for concurrent manipulation of data

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

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

yes

using SASL (Simple Authentication and Security Layer) protocol

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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.