DBMS > BigObject vs. Google Cloud Datastore vs. Riak TS vs. RocksDB vs. Tkrzw

System Properties Comparison BigObject vs. Google Cloud Datastore vs. Riak TS vs. RocksDB vs. Tkrzw

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for real-time computations and queries

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

Riak TS is a distributed NoSQL database optimized for time series data and based on Riak KV

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

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

Primary database model

Relational DBMS

a hierachical model (tree) can be imposed

Document store

Time Series DBMS

Key-value store

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

Score	0.19
Rank	#329	Overall
	#146	Relational DBMS

Score	4.36
Rank	#72	Overall
	#12	Document stores

Score	0.28
Rank	#307	Overall
	#27	Time Series DBMS

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Score	0.07
Rank	#372	Overall
	#57	Key-value stores

Website

bigobject.io

cloud.google.com/datastore

rocksdb.org

dbmx.net/tkrzw

Technical documentation

docs.bigobject.io

cloud.google.com/datastore/docs

www.tiot.jp/riak-docs/riak/ts/latest

github.com/facebook/rocksdb/wiki

Developer

BigObject, Inc.

Google

Open Source, formerly Basho Technologies

Facebook, Inc.

Mikio Hirabayashi

Initial release

2015

2008

2015

2013

2020

Current release

3.0.0, September 2022

9.2.1, May 2024

0.9.3, August 2020

License

Commercial or Open Source

commercial

free community edition available

commercial

Open Source

BSD

Open Source

Apache Version 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

Erlang

C++

Server operating systems

Linux

distributed as a docker-image
OS X

distributed as a docker-image (boot2docker)
Windows

distributed as a docker-image (boot2docker)

hosted

Linux
OS X

Linux

Linux
macOS

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

yes, details here

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

restricted

SQL

Support of SQL

SQL-like DML and DDL statements

SQL-like query language (GQL)

yes, limited

APIs and other access methods

fluentd
ODBC
RESTful HTTP API

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

HTTP API
Native Erlang Interface

C++ API
Java API

Supported programming languages

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

C
C++
Go
Java
Perl
Python
Ruby

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

Lua

using Google App Engine

Erlang

Triggers

Callbacks using the Google Apps Engine

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication using Paxos

selectable replication factor

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

automatically between fact table and dimension tables

yes

via ReferenceProperties or Ancestor paths

links between datasets can be stored

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

yes

Concurrency

Support for concurrent manipulation of data

yes

Read/write lock on objects (tables, trees)

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

using specific database classes

User concepts

Access control

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

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.