DBMS > Apache Druid vs. GeoSpock vs. RocksDB vs. SAP SQL Anywhere vs. Splunk

System Properties Comparison Apache Druid vs. GeoSpock vs. RocksDB vs. SAP SQL Anywhere vs. Splunk

Editorial information provided by DB-Engines

Name

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

Description

Open-source analytics data store designed for sub-second OLAP queries on high dimensionality and high cardinality data

Spatial and temporal data processing engine for extreme data scale

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

RDBMS database and synchronization technologies for server, desktop, remote office, and mobile environments

Analytics Platform for Big Data

Primary database model

Relational DBMS
Time Series DBMS

Secondary database models

Time Series DBMS

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

Score	3.34
Rank	#88	Overall
	#48	Relational DBMS
	#7	Time Series DBMS

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Score	4.25
Rank	#79	Overall
	#43	Relational DBMS

Score	86.45
Rank	#14	Overall
	#2	Search engines

Website

druid.apache.org

geospock.com

rocksdb.org

www.sap.com/products/technology-platform/sql-anywhere.html

www.splunk.com

Technical documentation

druid.apache.org/docs/latest/design

github.com/facebook/rocksdb/wiki

help.sap.com/docs/SAP_SQL_Anywhere

docs.splunk.com/Documentation/Splunk

Developer

Apache Software Foundation and contributors

GeoSpock

Facebook, Inc.

SAP

formerly Sybase

Splunk Inc.

Initial release

2012

2013

1992

2003

Current release

29.0.1, April 2024

2.0, September 2019

9.2.1, May 2024

17, July 2015

License

Commercial or Open Source

Open Source

Apache license v2

commercial

Open Source

BSD

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

C++

Server operating systems

Linux
OS X
Unix

hosted

Linux

AIX
HP-UX
Linux
OS X
Solaris
Windows

Linux
OS X
Solaris
Windows

Data scheme

yes

schema-less columns are supported

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

yes

temporal, categorical

yes

SQL

Support of SQL

SQL for querying

ANSI SQL for query only (using Presto)

yes

Splunk Search Processing Language for search commands

APIs and other access methods

JDBC
RESTful HTTP/JSON API

JDBC

C++ API
Java API

ADO.NET
HTTP API
JDBC
ODBC

HTTP REST

Supported programming languages

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

C
C++
Go
Java
Perl
Python
Ruby

C
C#
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

C#
Java
JavaScript
PHP
Python
Ruby

Server-side scripts

Stored procedures

yes, in C/C++, Java, .Net or Perl

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

Automatic sharding

horizontal partitioning

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes, via HDFS, S3 or other storage engines

yes

Source-replica replication

Database mirroring

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

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

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

User concepts

Access control

RBAC using LDAP or Druid internals for users and groups for read/write by datasource and system

Access rights for users can be defined per table

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.