DBMS > Amazon Neptune vs. Amazon Redshift vs. Atos Standard Common Repository vs. EXASOL vs. SiteWhere

System Properties Comparison Amazon Neptune vs. Amazon Redshift vs. Atos Standard Common Repository vs. EXASOL vs. SiteWhere

Editorial information provided by DB-Engines

Name

This system has been discontinued and will be 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

Highly scalable database system, designed for managing session and subscriber data in modern mobile communication networks

High-performance, in-memory, MPP database specifically designed for in-memory analytics.

M2M integration platform for persisting/querying time series data

Primary database model

Graph DBMS
RDF store

Relational DBMS

Document store
Key-value store

Relational DBMS

Time Series DBMS

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

Score	2.29
Rank	#113	Overall
	#9	Graph DBMS
	#5	RDF stores

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	1.76
Rank	#139	Overall
	#62	Relational DBMS

Score	0.06
Rank	#383	Overall
	#43	Time Series DBMS

Website

aws.amazon.com/neptune

aws.amazon.com/redshift

atos.net/en/convergence-creators/portfolio/standard-common-repository

www.exasol.com

github.com/sitewhere/sitewhere

Technical documentation

aws.amazon.com/neptune/developer-resources

docs.aws.amazon.com/redshift

www.exasol.com/resources

sitewhere1.sitewhere.io/index.html

Developer

Amazon

Amazon (based on PostgreSQL)

Atos Convergence Creators

Exasol

SiteWhere

Initial release

2017

2012

2016

2000

2010

Current release

1703

License

Commercial or Open Source

commercial

Open Source

Common Public Attribution License Version 1.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

Server operating systems

hosted

Linux

Linux
OS X
Windows

Data scheme

schema-free

yes

Schema and schema-less with LDAP views

yes

predefined scheme

Typing

predefined data types such as float or date

yes

optional

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.

yes

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

APIs and other access methods

OpenCypher
RDF 1.1 / SPARQL 1.1
TinkerPop Gremlin

JDBC
ODBC

LDAP

.Net
JDBC
ODBC
WebSocket

HTTP REST

Supported programming languages

C#
Go
Java
JavaScript
PHP
Python
Ruby
Scala

All languages supporting JDBC/ODBC

All languages with LDAP bindings

Java
Lua
Python
R

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

cell division

Sharding

based on HBase

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

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

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

Atomic execution of specific operations

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

LDAP bind authentication

Access rights for users, groups and roles according to SQL-standard

Users with fine-grained authorization concept

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.