DBMS > Amazon Redshift vs. Apache IoTDB vs. Dgraph vs. EsgynDB vs. jBASE

System Properties Comparison Amazon Redshift vs. Apache IoTDB vs. Dgraph vs. EsgynDB vs. jBASE

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

An IoT native database with high performance for data management and analysis, deployable on the edge and the cloud and integrated with Hadoop, Spark and Flink

Distributed and scalable native Graph DBMS

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

A robust multi-value DBMS comprising development tools and middleware

Primary database model

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	1.18
Rank	#173	Overall
	#15	Time Series DBMS

Score	1.45
Rank	#156	Overall
	#15	Graph DBMS

Score	0.16
Rank	#329	Overall
	#146	Relational DBMS

Score	1.41
Rank	#159	Overall
	#3	Multivalue DBMS

Website

aws.amazon.com/redshift

iotdb.apache.org

dgraph.io

www.esgyn.cn

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-jbase

Technical documentation

docs.aws.amazon.com/redshift

iotdb.apache.org/UserGuide/Master/QuickStart/QuickStart.html

dgraph.io/docs

docs.rocketsoftware.com/bundle?labelkey=jbase_5.9

Developer

Amazon (based on PostgreSQL)

Apache Software Foundation

Dgraph Labs, Inc.

Esgyn

Rocket Software (formerly Zumasys)

Initial release

2012

2018

2016

2015

1991

Current release

1.1.0, April 2023

5.7

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

Open Source

Apache 2.0

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

Java

C++, Java

Server operating systems

hosted

All OS with a Java VM (>= 1.8)

Linux
OS X
Windows

Linux

AIX
Linux
Windows

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

optional

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.

yes

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like query language

yes

Embedded SQL for jBASE in BASIC

APIs and other access methods

JDBC
ODBC

JDBC
Native API

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

ADO.NET
JDBC
ODBC

JDBC
ODBC
Proprietary protocol
RESTful HTTP API
SOAP-based API

Supported programming languages

All languages supporting JDBC/ODBC

C
C#
C++
Go
Java
Python
Scala

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

All languages supporting JDBC/ODBC/ADO.Net

.Net
Basic
Jabbascript
Java

Server-side scripts

Stored procedures

user defined functions

in Python

yes

Java Stored Procedures

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning (by time range) + vertical partitioning (by deviceId)

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication methods; using Raft/IoTConsensus algorithm to ensure strong/eventual data consistency among multiple replicas

Synchronous replication via Raft

Multi-source replication between multi datacenters

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Integration with Hadoop and Spark

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Strong Consistency with Raft

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

Transaction concepts

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

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

yes

Planned for future releases

fine grained access rights according to SQL-standard

Access rights can be defined down to the item level

More information provided by the system vendor

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.