DBMS > GBase vs. Google BigQuery vs. RavenDB vs. STSdb vs. ToroDB

System Properties Comparison GBase vs. Google BigQuery vs. RavenDB vs. STSdb vs. ToroDB

Editorial information provided by DB-Engines

Name

ToroDB seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Widely used RDBMS in China, including analytical, transactional, distributed transactional, and cloud-native data warehousing.

Large scale data warehouse service with append-only tables

Open Source Operational and Transactional Enterprise NoSQL Document Database

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

A MongoDB-compatible JSON document store, built on top of PostgreSQL

Primary database model

Secondary database models

Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	1.05
Rank	#186	Overall
	#86	Relational DBMS

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	2.84
Rank	#101	Overall
	#18	Document stores

Score	0.10
Rank	#357	Overall
	#51	Key-value stores

Website

www.gbase.cn

cloud.google.com/bigquery

ravendb.net

github.com/STSSoft/STSdb4

github.com/torodb/server

Technical documentation

cloud.google.com/bigquery/docs

ravendb.net/docs

Developer

General Data Technology Co., Ltd.

Google

Hibernating Rhinos

STS Soft SC

8Kdata

Initial release

2004

2010

2011

2016

Current release

GBase 8a, GBase 8s, GBase 8c

5.4, July 2022

4.0.8, September 2015

License

Commercial or Open Source

commercial

Open Source

AGPL version 3, commercial license available

Open Source

GPLv2, commercial license available

Open Source

AGPL-V3

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, Java, Python

Java

Server operating systems

Linux

hosted

Linux
macOS
Raspberry Pi
Windows

Windows

All OS with a Java 7 VM

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

primitive types and user defined types (classes)

yes

string, integer, double, boolean, date, object_id

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.

yes

Secondary indexes

yes

SQL

Support of SQL

Standard with numerous extensions

yes

SQL-like query language (RQL)

APIs and other access methods

ADO.NET
C API
JDBC
ODBC

RESTful HTTP/JSON API

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

.NET Client API

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

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

C#
Java

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning (by range, list and hash) and vertical partitioning

none

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication

none

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Since BigQuery is designed for querying data

ACID, Cluster-wide transaction available

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.

User concepts

Access control

yes

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

Authorization levels configured per client per database

Access rights for users and roles

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.