DBMS > Amazon Redshift vs. Atos Standard Common Repository vs. BigchainDB vs. SiteWhere vs. Splunk

System Properties Comparison Amazon Redshift vs. Atos Standard Common Repository vs. BigchainDB vs. SiteWhere vs. Splunk

Editorial information provided by DB-Engines

Name

This system has been discontinued and will be removed from the DB-Engines ranking.

Description

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

BigchainDB is scalable blockchain database offering decentralization, immutability and native assets

M2M integration platform for persisting/querying time series data

Analytics Platform for Big Data

Primary database model

Relational DBMS

Document store
Key-value store

Document store

Time Series DBMS

Search engine

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	0.79
Rank	#212	Overall
	#36	Document stores

Score	0.06
Rank	#356	Overall
	#35	Time Series DBMS

Score	86.45
Rank	#14	Overall
	#2	Search engines

Website

aws.amazon.com/redshift

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

www.bigchaindb.com

github.com/sitewhere/sitewhere

www.splunk.com

Technical documentation

docs.aws.amazon.com/redshift

bigchaindb.readthedocs.io/en/latest

sitewhere1.sitewhere.io/index.html

docs.splunk.com/Documentation/Splunk

Developer

Amazon (based on PostgreSQL)

Atos Convergence Creators

SiteWhere

Splunk Inc.

Initial release

2012

2016

2010

2003

Current release

1703

License

Commercial or Open Source

commercial

Open Source

AGPL v3

Open Source

Common Public Attribution License Version 1.0

commercial

Limited free edition and free developer edition available

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

Python

Java

Server operating systems

hosted

Linux

Linux
OS X
Windows

Linux
OS X
Solaris
Windows

Data scheme

yes

Schema and schema-less with LDAP views

schema-free

predefined scheme

yes

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

Splunk Search Processing Language for search commands

APIs and other access methods

JDBC
ODBC

LDAP

CLI Client
RESTful HTTP API

HTTP REST

Supported programming languages

All languages supporting JDBC/ODBC

All languages with LDAP bindings

Go
Haskell
Java
JavaScript
Python
Ruby

C#
Java
JavaScript
PHP
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

in Python

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

based on HBase

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

based on HBase

Multi-source 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 or Eventual Consistency depending on configuration

Immediate Consistency

Eventual Consistency

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

Atomic execution of specific operations

A 'Transaction' in Splunk has a different meaning: grouping related events into a single one for later searching

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes,with MongoDB ord RethinkDB

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

LDAP bind authentication

yes

Users with fine-grained authorization concept

Access rights for users and roles

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.