DBMS > GBase vs. GridDB vs. RocksDB vs. Sphinx vs. TimescaleDB

System Properties Comparison GBase vs. GridDB vs. RocksDB vs. Sphinx vs. TimescaleDB

Editorial information provided by DB-Engines

Name

Description

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

Scalable in-memory time series database optimized for IoT and Big Data

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

Open source search engine for searching in data from different sources, e.g. relational databases

A time series DBMS optimized for fast ingest and complex queries, based on PostgreSQL

Primary database model

Secondary database models

Key-value store
Relational DBMS

Relational DBMS

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

Score	1.07
Rank	#185	Overall
	#86	Relational DBMS

Score	1.95
Rank	#128	Overall
	#10	Time Series DBMS

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Score	5.98
Rank	#56	Overall
	#5	Search engines

Score	4.64
Rank	#71	Overall
	#4	Time Series DBMS

Website

Technical documentation

docs.griddb.net

github.com/facebook/rocksdb/wiki

sphinxsearch.com/docs

docs.timescale.com

Developer

General Data Technology Co., Ltd.

Toshiba Corporation

Facebook, Inc.

Sphinx Technologies Inc.

Timescale

Initial release

2004

2013

2001

2017

Current release

GBase 8a, GBase 8s, GBase 8c

5.1, August 2022

8.11.4, April 2024

3.5.1, February 2023

2.15.0, May 2024

License

Commercial or Open Source

commercial

Open Source

AGPL version 3 and Apache License, version 2.0 , commercial license (standard and advanced editions) also available

Open Source

BSD

Open Source

GPL version 2, commercial licence available

Open Source

Apache 2.0

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C, Java, Python

C++

Server operating systems

Linux

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Linux
OS X
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

numerical, string, blob, geometry, boolean, timestamp

numerics, strings, booleans, arrays, JSON blobs, geospatial dimensions, currencies, binary data, other complex data types

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

full-text index on all search fields

yes

SQL

Support of SQL

Standard with numerous extensions

SQL92, SQL-like TQL (Toshiba Query Language)

SQL-like query language (SphinxQL)

yes

full PostgreSQL SQL syntax

APIs and other access methods

ADO.NET
C API
JDBC
ODBC

JDBC
ODBC
Proprietary protocol
RESTful HTTP/JSON API

C++ API
Java API

Proprietary protocol

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Supported programming languages

C
C++
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

C
C++
Go
Java
Perl
Python
Ruby

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

user defined functions

user defined functions, PL/pgSQL, PL/Tcl, PL/Perl, PL/Python, PL/Java, PL/PHP, PL/R, PL/Ruby, PL/Scheme, PL/Unix shell

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

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

Sharding

horizontal partitioning

Sharding

Partitioning is done manually, search queries against distributed index is supported

yes, across time and space (hash partitioning) attributes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

yes

none

Source-replica replication with hot standby and reads on replicas

MapReduce

Offers an API for user-defined Map/Reduce methods

Connector for using GridDB as an input source and output destination for Hadoop MapReduce jobs

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate consistency within container, eventual consistency across containers

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

ACID at container level

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

The original contents of fields are not stored in the Sphinx index.

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

yes

Access rights for users can be defined per database

fine grained access rights according to SQL-standard

More information provided by the system vendor

Specific characteristics

GridDB is a highly scalable, in-memory time series database optimized for IoT and...
» more

Competitive advantages

1. Optimized for IoT Equipped with Toshiba's proprietary key-container data model...
» more

Typical application scenarios

Factory IoT, Automative Industry, Energy, BEMS, Smart Community, Monitoring system.
» more

Key customers

Denso International [see use case ] An Electric Power company [see use case ] Ishinomaki...
» more

Market metrics

GitHub trending repository
» more

Licensing and pricing models

Open Source license (AGPL v3 & Apache v2) Commercial license (subscription)
» more

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.