DBMS > Amazon Redshift vs. BoltDB vs. Graph Engine vs. Splunk

System Properties Comparison Amazon Redshift vs. BoltDB vs. Graph Engine vs. Splunk

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

Analytics Platform for Big Data

Primary database model

Relational DBMS

Key-value store

Graph DBMS
Key-value store

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.74
Rank	#220	Overall
	#31	Key-value stores

Score	0.61
Rank	#240	Overall
	#21	Graph DBMS
	#35	Key-value stores

Score	86.45
Rank	#14	Overall
	#2	Search engines

Website

aws.amazon.com/redshift

github.com/boltdb/bolt

www.graphengine.io

www.splunk.com

Technical documentation

docs.aws.amazon.com/redshift

www.graphengine.io/docs/manual

docs.splunk.com/Documentation/Splunk

Developer

Amazon (based on PostgreSQL)

Microsoft

Splunk Inc.

Initial release

2012

2013

2010

2003

License

Commercial or Open Source

commercial

Open Source

MIT License

Open Source

MIT License

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

.NET and C

Server operating systems

hosted

BSD
Linux
OS X
Solaris
Windows

.NET

Linux
OS X
Solaris
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

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

RESTful HTTP API

HTTP REST

Supported programming languages

All languages supporting JDBC/ODBC

C#
C++
F#
Visual Basic

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

none

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

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

Transaction concepts

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

ACID

yes

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

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

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