DBMS > Amazon Redshift vs. Elasticsearch vs. GeoSpock vs. Splunk

System Properties Comparison Amazon Redshift vs. Elasticsearch vs. GeoSpock vs. Splunk

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

GeoSpock seems to be discontinued. Therefore it will be excluded from the DB-Engines ranking.

Description

Large scale data warehouse service for use with business intelligence tools

A distributed, RESTful modern search and analytics engine based on Apache Lucene

Elasticsearch lets you perform and combine many types of searches such as structured, unstructured, geo, and metric

Spatial and temporal data processing engine for extreme data scale

Analytics Platform for Big Data

Primary database model

Secondary database models

Document store
Spatial DBMS
Vector DBMS

Time Series DBMS

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	135.35
Rank	#7	Overall
	#1	Search engines

Score	86.45
Rank	#14	Overall
	#2	Search engines

Website

aws.amazon.com/redshift

www.elastic.co/elasticsearch

geospock.com

www.splunk.com

Technical documentation

docs.aws.amazon.com/redshift

www.elastic.co/guide/en/elasticsearch/reference/current/index.html

docs.splunk.com/Documentation/Splunk

Developer

Amazon (based on PostgreSQL)

Elastic

GeoSpock

Splunk Inc.

Initial release

2012

2010

2003

Current release

8.6, January 2023

2.0, September 2019

License

Commercial or Open Source

commercial

Open Source

Elastic 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

Java

Java, Javascript

Server operating systems

hosted

All OS with a Java VM

hosted

Linux
OS X
Solaris
Windows

Data scheme

yes

schema-free

Flexible type definitions. Once a type is defined, it is persistent

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

All search fields are automatically indexed

temporal, categorical

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like query language

ANSI SQL for query only (using Presto)

Splunk Search Processing Language for search commands

APIs and other access methods

JDBC
ODBC

Java API
RESTful HTTP/JSON API

JDBC

HTTP REST

Supported programming languages

All languages supporting JDBC/ODBC

.Net
Groovy
Community Contributed Clients
Java
JavaScript
Perl
PHP
Python
Ruby

C#
Java
JavaScript
PHP
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

in Python

yes

Triggers

yes

by using the 'percolation' feature

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Automatic sharding

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

ES-Hadoop Connector

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Synchronous doc based replication. Get by ID may show delays up to 1 sec. Configurable write consistency: one, quorum, all

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

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

Memcached and Redis integration

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users can be defined per table

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.