DBMS > Drizzle vs. GridDB vs. STSdb vs. ToroDB

System Properties Comparison Drizzle vs. GridDB vs. STSdb vs. ToroDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

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

Description

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

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

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

Key-value store
Relational DBMS

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

Score	2.02
Rank	#132	Overall
	#11	Time Series DBMS

Score	0.06
Rank	#365	Overall
	#55	Key-value stores

Website

griddb.net

github.com/STSSoft/STSdb4

github.com/torodb/server

Technical documentation

docs.griddb.net

Developer

Drizzle project, originally started by Brian Aker

Toshiba Corporation

STS Soft SC

8Kdata

Initial release

2008

2013

2011

2016

Current release

7.2.4, September 2012

5.1, August 2022

4.0.8, September 2015

License

Commercial or Open Source

Open Source

GNU GPL

Open Source

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

Open Source

GPLv2, commercial license available

Open Source

AGPL-V3

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

Server operating systems

FreeBSD
Linux
OS X

Linux

Windows

All OS with a Java 7 VM

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

numerical, string, blob, geometry, boolean, timestamp

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.

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

SQL92, SQL-like TQL (Toshiba Query Language)

APIs and other access methods

JDBC

JDBC
ODBC
Proprietary protocol
RESTful HTTP/JSON API

.NET Client API

Supported programming languages

C
C++
Java
PHP

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

C#
Java

Server-side scripts

Stored procedures

Triggers

hooks for callbacks inside the server can be used.

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Source-replica replication

none

Source-replica replication

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 within container, eventual consistency across containers

Eventual Consistency
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

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.

yes

User concepts

Access control

Pluggable authentication mechanisms

e.g. LDAP, HTTP

Access rights for users can be defined per database

Access rights for users and roles

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

MySQL won the April ranking; did its forks follow?
1 April 2015, Paul Andlinger

Has MySQL finally lost its mojo?
1 July 2013, Matthias Gelbmann

show all

Recent citations in the news

General Availability of GridDB® 5.6 Enterprise Edition ~ Equipped with the "site-to-site database replication" function ...
17 April 2024, global.toshiba

General Availability of GridDB® 5.5 Enterprise Edition ~Enhancing the efficiency of IoT system development and ...
16 January 2024, global.toshiba

General Availability of GridDB 5.3 Enterprise Edition ~ Major Enhancement in IoT and Time Series Data Analysis ...
16 May 2023, global.toshiba

Toshiba launches cloudy managed IoT database service running its own GridDB
8 April 2021, The Register

Toshiba's Distributed Database GridDB(R) Now Features Scale-Out and Scale-Up combo for Petabyte-scale Data ...
3 December 2019, global.toshiba

provided by Google News

Share this page