DBMS > Google BigQuery vs. KairosDB vs. KeyDB vs. Transbase

System Properties Comparison Google BigQuery vs. KairosDB vs. KeyDB vs. Transbase

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

Distributed Time Series DBMS based on Cassandra or H2

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

A resource-optimized, high-performance, universally applicable RDBMS

Primary database model

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

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	0.62
Rank	#239	Overall
	#20	Time Series DBMS

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

Score	0.11
Rank	#341	Overall
	#150	Relational DBMS

Website

cloud.google.com/bigquery

github.com/kairosdb/kairosdb

github.com/Snapchat/KeyDB
keydb.dev

www.transaction.de/en/products/transbase.html

Technical documentation

cloud.google.com/bigquery/docs

kairosdb.github.io

docs.keydb.dev

www.transaction.de/en/products/transbase/features.html

Developer

Google

EQ Alpha Technology Ltd.

Transaction Software GmbH

Initial release

2010

2013

2019

1987

Current release

1.2.2, November 2018

Transbase 8.3, 2022

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

BSD-3

commercial

free development license

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

C and C++

Server operating systems

hosted

Linux
OS X
Windows

Linux

FreeBSD
Linux
macOS
Solaris
Windows

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

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

SQL

Support of SQL

yes

APIs and other access methods

RESTful HTTP/JSON API

Graphite protocol
HTTP REST
Telnet API

Proprietary protocol

RESP - REdis Serialization Protoco

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

Java
JavaScript

Node.js
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

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Server-side scripts

Stored procedures

user defined functions

in JavaScript

Lua

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

based on Cassandra

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

based on Cassandra

Multi-source replication
Source-replica replication

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

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

Optimistic locking, atomic execution of commands blocks and scripts

yes

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)

simple password-based access control

simple password-based access control and ACL

fine grained access rights according to SQL-standard

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.