DBMS > GridDB vs. RocksDB vs. TerminusDB vs. TypeDB

System Properties Comparison GridDB vs. RocksDB vs. TerminusDB vs. TypeDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

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

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

TypeDB is a strongly-typed database with a rich and logical type system and TypeQL as its query language

Primary database model

Time Series DBMS

Key-value store

Graph DBMS

Graph DBMS
Relational DBMS

Often described as a 'hyper-relational' database, since it implements the 'Entity-Relationship Paradigm' to manage complex data structures and ontologies.

Secondary database models

Key-value store
Relational DBMS

Document store
RDF store

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

Score	1.95
Rank	#128	Overall
	#10	Time Series DBMS

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

Score	0.17
Rank	#325	Overall
	#29	Graph DBMS

Score	0.65
Rank	#234	Overall
	#20	Graph DBMS
	#107	Relational DBMS

Website

Technical documentation

docs.griddb.net

github.com/facebook/rocksdb/wiki

terminusdb.github.io/terminusdb/#

typedb.com/docs

Developer

Toshiba Corporation

Facebook, Inc.

DataChemist Ltd.

Vaticle

Initial release

2013

2018

2016

Current release

5.1, August 2022

8.11.4, April 2024

11.0.0, January 2023

2.26.3, January 2024

License

Commercial or Open Source

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 V3

Open Source

GPL Version 3, commercial licenses available

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

Prolog, Rust

Java

Server operating systems

Linux

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

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

SQL

Support of SQL

SQL92, SQL-like TQL (Toshiba Query Language)

SQL-like query language (WOQL)

APIs and other access methods

JDBC
ODBC
Proprietary protocol
RESTful HTTP/JSON API

C++ API
Java API

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

gRPC protocol
TypeDB Console (shell)
TypeDB Studio (Visualisation software- previously TypeDB Workbase)

Supported programming languages

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

C
C++
Go
Java
Perl
Python
Ruby

JavaScript
Python

All JVM based languages
Groovy
Java
JavaScript (Node.js)
Python
Scala

Server-side scripts

Stored procedures

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

Graph Partitioning

Sharding

by using Cassandra

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

Journaling Streams

Multi-source replication

by using Cassandra

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

yes

by using Apache Kafka and Apache Zookeeper

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate consistency within container, eventual consistency across containers

Immediate Consistency

Foreign keys

Referential integrity

yes

substituted by the relationship feature

Transaction concepts

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

ACID at container level

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

in-memory journaling

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 rights for users can be defined per database

Role-based access control

yes

at REST API level; other APIs in progress

More information provided by the system vendor

Specific characteristics

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

TypeDB is a polymorphic database with a conceptual data model, a strong subtyping...
» more

Competitive advantages

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

TypeDB provides a new level of expressivity, extensibility, interoperability, and...
» more

Typical application scenarios

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

Life sciences : TypeDB makes working with biological data much easier and accelerates...
» 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

Apache f or language drivers, and AGPL and Commercial for the database server. The...
» 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.