DBMS > Apache Druid vs. SAP SQL Anywhere vs. Splunk vs. SQLite

System Properties Comparison Apache Druid vs. SAP SQL Anywhere vs. Splunk vs. SQLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

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

Analytics Platform for Big Data

Widely used embeddable, in-process RDBMS

Primary database model

Relational DBMS
Time Series DBMS

Relational DBMS

Search engine

Relational DBMS

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

Score	3.29
Rank	#95	Overall
	#49	Relational DBMS
	#7	Time Series DBMS

Score	4.57
Rank	#78	Overall
	#43	Relational DBMS

Score	88.71
Rank	#14	Overall
	#2	Search engines

Score	116.01
Rank	#10	Overall
	#7	Relational DBMS

Website

druid.apache.org

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

www.splunk.com

www.sqlite.org

Technical documentation

druid.apache.org/docs/latest/design

help.sap.com/docs/SAP_SQL_Anywhere

docs.splunk.com/Documentation/Splunk

www.sqlite.org/docs.html

Developer

Apache Software Foundation and contributors

SAP

formerly Sybase

Splunk Inc.

Dwayne Richard Hipp

Initial release

2012

1992

2003

2000

Current release

29.0.1, April 2024

17, July 2015

3.45.2 (12 March 2024), March 2024

License

Commercial or Open Source

Open Source

Apache license v2

commercial

Limited free edition and free developer edition available

Open Source

Public Domain

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

Server operating systems

Linux
OS X
Unix

AIX
HP-UX
Linux
OS X
Solaris
Windows

Linux
OS X
Solaris
Windows

server-less

Data scheme

yes

schema-less columns are supported

yes

dynamic column types

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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

SQL

Support of SQL

SQL for querying

yes

Splunk Search Processing Language for search commands

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC
RESTful HTTP/JSON API

ADO.NET
HTTP API
JDBC
ODBC

HTTP REST

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

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

C#
Java
JavaScript
PHP
Python
Ruby

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

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

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes, via HDFS, S3 or other storage engines

Source-replica replication

Database mirroring

Multi-source replication

none

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

ACID

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

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

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.