DBMS > Amazon Redshift vs. Geode vs. GridDB vs. TinkerGraph

System Properties Comparison Amazon Redshift vs. Geode vs. GridDB vs. TinkerGraph

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

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

A lightweight, in-memory graph engine that serves as a reference implementation of the TinkerPop3 API

Primary database model

Secondary database models

Key-value store
Relational DBMS

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	1.86
Rank	#134	Overall
	#24	Key-value stores

Score	2.09
Rank	#120	Overall
	#10	Time Series DBMS

Score	0.13
Rank	#345	Overall
	#35	Graph DBMS

Website

aws.amazon.com/redshift

geode.apache.org

griddb.net

tinkerpop.apache.org/docs/current/reference/#tinkergraph-gremlin

Technical documentation

docs.aws.amazon.com/redshift

geode.apache.org/docs

docs.griddb.net

Developer

Amazon (based on PostgreSQL)

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

Toshiba Corporation

Initial release

2012

2002

2013

2009

Current release

1.1, February 2017

5.1, August 2022

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

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

Open Source

Apache 2.0

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

Java

C++

Java

Server operating systems

hosted

All OS with a Java VM

the JDK (8 or later) is also required

Linux

Data scheme

yes

schema-free

yes

schema-free

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

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like query language (OQL)

SQL92, SQL-like TQL (Toshiba Query Language)

APIs and other access methods

JDBC
ODBC

Java Client API
Memcached protocol
RESTful HTTP API

JDBC
ODBC
Proprietary protocol
RESTful HTTP/JSON API

TinkerPop 3

Supported programming languages

All languages supporting JDBC/ODBC

.Net
All JVM based languages
C++
Groovy
Java
Scala

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

Groovy
Java

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions

Triggers

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication

Source-replica replication

none

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

Eventual Consistency

Immediate consistency within container, eventual consistency across containers

none

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

Relationships in graphs

Transaction concepts

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

ACID

yes, on a single node

ACID at container level

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

optional

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

Access rights per client and object definable

Access rights for users can be defined per database

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.