DBMS > Amazon Redshift vs. Apache Drill vs. GridDB vs. RDF4J

System Properties Comparison Amazon Redshift vs. Apache Drill vs. GridDB vs. RDF4J

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

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

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

RDF4J is a Java framework for processing RDF data, supporting both memory-based and a disk-based storage.

Primary database model

Relational DBMS

Document store
Relational DBMS

Time Series DBMS

RDF store

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.95
Rank	#127	Overall
	#23	Document stores
	#60	Relational DBMS

Score	1.95
Rank	#128	Overall
	#10	Time Series DBMS

Score	0.69
Rank	#230	Overall
	#9	RDF stores

Website

aws.amazon.com/redshift

drill.apache.org

griddb.net

rdf4j.org

Technical documentation

docs.aws.amazon.com/redshift

drill.apache.org/docs

docs.griddb.net

rdf4j.org/documentation

Developer

Amazon (based on PostgreSQL)

Apache Software Foundation

Toshiba Corporation

Since 2016 officially forked into an Eclipse project, former developer was Aduna Software.

Initial release

2012

2013

2004

Current release

1.20.3, January 2023

5.1, August 2022

License

Commercial or Open Source

commercial

Open Source

Apache Version 2

Open Source

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

Open Source

Eclipse Distribution License (EDL), v1.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

C++

Java

Server operating systems

hosted

Linux
OS X
Windows

Linux

Linux
OS X
Unix
Windows

Data scheme

yes

schema-free

yes

RDF Schemas

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 SELECT statement is SQL:2003 compliant

SQL92, SQL-like TQL (Toshiba Query Language)

APIs and other access methods

JDBC
ODBC

JDBC
ODBC
RESTful HTTP API

JDBC
ODBC
Proprietary protocol
RESTful HTTP/JSON API

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

Supported programming languages

All languages supporting JDBC/ODBC

C++

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

Java
PHP
Python

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

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

none

Immediate consistency within container, eventual consistency across containers

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

Isolation support depends on the API used

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Depending on the underlying data source

yes

in-memory storage is supported as well

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

Depending on the underlying data source

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Depending on the underlying data source

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.