DBMS > Amazon Redshift vs. jBASE vs. Postgres-XL vs. Prometheus vs. Splunk

System Properties Comparison Amazon Redshift vs. jBASE vs. Postgres-XL vs. Prometheus vs. Splunk

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

A robust multi-value DBMS comprising development tools and middleware

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

Open-source Time Series DBMS and monitoring system

Analytics Platform for Big Data

Primary database model

Secondary database models

Document store
Spatial DBMS

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	1.49
Rank	#156	Overall
	#3	Multivalue DBMS

Score	0.53
Rank	#254	Overall
	#117	Relational DBMS

Score	7.69
Rank	#50	Overall
	#3	Time Series DBMS

Score	89.10
Rank	#14	Overall
	#2	Search engines

Website

aws.amazon.com/redshift

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

www.postgres-xl.org

prometheus.io

www.splunk.com

Technical documentation

docs.aws.amazon.com/redshift

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

www.postgres-xl.org/documentation

prometheus.io/docs

docs.splunk.com/Documentation/Splunk

Developer

Amazon (based on PostgreSQL)

Rocket Software (formerly Zumasys)

Splunk Inc.

Initial release

2012

1991

2014

since 2012, originally named StormDB

2015

2003

Current release

5.7

10 R1, October 2018

License

Commercial or Open Source

commercial

Open Source

Mozilla public license

Open Source

Apache 2.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

Server operating systems

hosted

AIX
Linux
Windows

Linux
macOS

Linux
Windows

Linux
OS X
Solaris
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

optional

yes

Numeric data only

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

XML type, but no XML query functionality

Import of XML data possible

yes

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

Embedded SQL for jBASE in BASIC

yes

distributed, parallel query execution

Splunk Search Processing Language for search commands

APIs and other access methods

JDBC
ODBC

JDBC
ODBC
Proprietary protocol
RESTful HTTP API
SOAP-based API

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

RESTful HTTP/JSON API

HTTP REST

Supported programming languages

All languages supporting JDBC/ODBC

.Net
Basic
Jabbascript
Java

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

.Net
C++
Go
Haskell
Java
JavaScript (Node.js)
Python
Ruby

C#
Java
JavaScript
PHP
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

in Python

yes

user defined functions

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

by Federation

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

none

Eventual 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

MVCC

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

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

Access rights can be defined down to the item level

fine grained access rights according to SQL-standard

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.