DBMS > Google BigQuery vs. Graph Engine vs. RocksDB vs. STSdb

System Properties Comparison Google BigQuery vs. Graph Engine vs. RocksDB vs. STSdb

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

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

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

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Primary database model

Relational DBMS

Graph DBMS
Key-value store

Key-value store

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

Score	52.67
Rank	#19	Overall
	#13	Relational DBMS

Score	0.56
Rank	#241	Overall
	#21	Graph DBMS
	#34	Key-value stores

Score	2.84
Rank	#97	Overall
	#16	Key-value stores

Score	0.03
Rank	#365	Overall
	#54	Key-value stores

Website

cloud.google.com/bigquery

www.graphengine.io

rocksdb.org

github.com/STSSoft/STSdb4

Technical documentation

cloud.google.com/bigquery/docs

www.graphengine.io/docs/manual

github.com/facebook/rocksdb/wiki

Developer

Google

Microsoft

Facebook, Inc.

STS Soft SC

Initial release

2010

2013

2011

Current release

9.4.0, June 2024

4.0.8, September 2015

License

Commercial or Open Source

commercial

Open Source

MIT License

Open Source

BSD

Open Source

GPLv2, commercial license available

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

.NET and C

C++

Server operating systems

hosted

.NET

Linux

Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

primitive types and user defined types (classes)

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

SQL

Support of SQL

yes

APIs and other access methods

RESTful HTTP/JSON API

RESTful HTTP API

C++ API
Java API

.NET Client API

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C#
C++
F#
Visual Basic

C
C++
Go
Java
Perl
Python
Ruby

C#
Java

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

Triggers

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate 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

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

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)

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.