DBMS > Amazon Redshift vs. Dgraph vs. GridDB vs. ToroDB vs. VelocityDB

System Properties Comparison Amazon Redshift vs. Dgraph vs. GridDB vs. ToroDB vs. VelocityDB

Editorial information provided by DB-Engines

Name

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

Description

Large scale data warehouse service for use with business intelligence tools

Distributed and scalable native Graph DBMS

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

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

A .NET Object Database that can be embedded/distributed and extended to a graph data model (VelocityGraph)

Primary database model

Graph DBMS
Object oriented DBMS

Secondary database models

Key-value store
Relational DBMS

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	1.45
Rank	#156	Overall
	#15	Graph DBMS

Score	1.95
Rank	#128	Overall
	#10	Time Series DBMS

Score	0.05
Rank	#358	Overall
	#36	Graph DBMS
	#16	Object oriented DBMS

Website

aws.amazon.com/redshift

dgraph.io

griddb.net

github.com/torodb/server

velocitydb.com

Technical documentation

docs.aws.amazon.com/redshift

dgraph.io/docs

docs.griddb.net

velocitydb.com/UserGuide

Developer

Amazon (based on PostgreSQL)

Dgraph Labs, Inc.

Toshiba Corporation

8Kdata

VelocityDB Inc

Initial release

2012

2016

2013

2016

2011

Current release

5.1, August 2022

7.x

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

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

Open Source

AGPL-V3

commercial

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

Server operating systems

hosted

Linux
OS X
Windows

Linux

All OS with a Java 7 VM

Any that supports .NET

Data scheme

yes

schema-free

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

numerical, string, blob, geometry, boolean, timestamp

yes

string, integer, double, boolean, date, object_id

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

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL92, SQL-like TQL (Toshiba Query Language)

APIs and other access methods

JDBC
ODBC

GraphQL query language
gRPC (using protocol buffers) API
HTTP API

JDBC
ODBC
Proprietary protocol
RESTful HTTP/JSON API

.Net

Supported programming languages

All languages supporting JDBC/ODBC

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

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

.Net

Server-side scripts

Stored procedures

user defined functions

in Python

Triggers

yes

Callbacks are triggered when data changes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Synchronous replication via Raft

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

Immediate consistency within container, eventual consistency across containers

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

Transaction concepts

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

ACID

ACID at container level

ACID

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

fine grained access rights according to SQL-standard

Planned for future releases

Access rights for users can be defined per database

Access rights for users and roles

Based on Windows Authentication

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.