DBMS > Amazon Neptune vs. Amazon Redshift vs. DolphinDB vs. IRONdb vs. Yaacomo

System Properties Comparison Amazon Neptune vs. Amazon Redshift vs. DolphinDB vs. IRONdb vs. Yaacomo

Editorial information provided by DB-Engines

Name

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

Yaacomo seems to be discontinued and is removed from the DB-Engines ranking

Description

Fast, reliable graph database built for the cloud

Large scale data warehouse service for use with business intelligence tools

DolphinDB is a high performance Time Series DBMS. It is integrated with an easy-to-use fully featured programming language and a high-volume high-velocity streaming analytics system. It offers operational simplicity, scalability, fault tolerance, and concurrency.

A distributed Time Series DBMS with a focus on scalability, fault tolerance and operational simplicity

OpenCL based in-memory RDBMS, designed for efficiently utilizing the hardware via parallel computing

Primary database model

Secondary database models

Relational DBMS

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

Score	2.20
Rank	#119	Overall
	#9	Graph DBMS
	#5	RDF stores

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	4.13
Rank	#80	Overall
	#6	Time Series DBMS

Website

aws.amazon.com/neptune

aws.amazon.com/redshift

www.dolphindb.com

www.circonus.com/solutions/time-series-database/

yaacomo.com

Technical documentation

aws.amazon.com/neptune/developer-resources

docs.aws.amazon.com/redshift

docs.dolphindb.cn/en/help200/index.html

docs.circonus.com/irondb/category/getting-started

Developer

Amazon

Amazon (based on PostgreSQL)

DolphinDB, Inc

Circonus LLC.

Q2WEB GmbH

Initial release

2017

2012

2018

2017

2009

Current release

v2.00.4, January 2022

V0.10.20, January 2018

License

Commercial or Open Source

commercial

free community version available

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++

C and C++

Server operating systems

hosted

Linux
Windows

Linux

Android
Linux
Windows

Data scheme

schema-free

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

text, numeric, histograms

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

SQL-like query language (Circonus Analytics Query Language: CAQL)

yes

APIs and other access methods

OpenCypher
RDF 1.1 / SPARQL 1.1
TinkerPop Gremlin

JDBC
ODBC

JDBC
JSON over HTTP
Kafka
MQTT (Message Queue Telemetry Transport)
ODBC
OPC DA
OPC UA
RabbitMQ
WebSocket

HTTP API

JDBC
ODBC

Supported programming languages

C#
Go
Java
JavaScript
PHP
Python
Ruby
Scala

All languages supporting JDBC/ODBC

C#
C++
Go
Java
JavaScript
MatLab
Python
R
Rust

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript
JavaScript (Node.js)
Lisp
Lua
Perl
PHP
Python
R
Ruby
Rust
Scala

Server-side scripts

Stored procedures

user defined functions

in Python

yes

yes, in Lua

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning

Automatic, metric affinity per node

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-availability zones high availability, asynchronous replication for up to 15 read replicas within a single region. Global database clusters consists of a primary write DB cluster in one region, and up to five secondary read DB clusters in different regions. Each secondary region can have up to 16 reader instances.

yes

configurable replication factor, datacenter aware

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate consistency per node, eventual consistency across nodes

Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

yes

informational only, not enforced by the system

yes

Transaction concepts

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

ACID

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

with encyption-at-rest

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

Access rights for users and roles can be defined via the AWS Identity and Access Management (IAM)

fine grained access rights according to SQL-standard

Administrators, Users, Groups

fine grained access rights according to SQL-standard

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.