DBMS > Apache Druid vs. Ignite vs. SAP HANA vs. Splunk

System Properties Comparison Apache Druid vs. Ignite vs. SAP HANA vs. Splunk

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

Apache Ignite is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads, delivering in-memory speeds at petabyte scale.

In-memory, column based data store. Available as appliance or cloud service

Analytics Platform for Big Data

Primary database model

Relational DBMS
Time Series DBMS

Key-value store
Relational DBMS

Relational DBMS

Search engine

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	3.25
Rank	#90	Overall
	#47	Relational DBMS
	#7	Time Series DBMS

Score	3.11
Rank	#96	Overall
	#15	Key-value stores
	#49	Relational DBMS

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Score	89.10
Rank	#14	Overall
	#2	Search engines

Website

druid.apache.org

ignite.apache.org

www.sap.com/products/hana.html

www.splunk.com

Technical documentation

druid.apache.org/docs/latest/design

apacheignite.readme.io/docs

help.sap.com/hana

docs.splunk.com/Documentation/Splunk

Developer

Apache Software Foundation and contributors

Apache Software Foundation

SAP

Splunk Inc.

Initial release

2012

2015

2010

2003

Current release

29.0.1, April 2024

Apache Ignite 2.6

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

Apache license v2

Open Source

Apache 2.0

commercial

Limited free edition and free developer edition available

Cloud-based only

Only available as a cloud service

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Java

C++, Java, .Net

Server operating systems

Linux
OS X
Unix

Linux
OS X
Solaris
Windows

Appliance or cloud-service

Linux
OS X
Solaris
Windows

Data scheme

yes

schema-less columns are supported

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

SQL

Support of SQL

SQL for querying

ANSI-99 for query and DML statements, subset of DDL

yes

Splunk Search Processing Language for search commands

APIs and other access methods

JDBC
RESTful HTTP/JSON API

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

JDBC
ODBC

HTTP REST

Supported programming languages

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

C#
C++
Java
PHP
Python
Ruby
Scala

C#
Java
JavaScript
PHP
Python
Ruby

Server-side scripts

Stored procedures

yes (compute grid and cache interceptors can be used instead)

SQLScript, R

yes

Triggers

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

Sharding

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes, via HDFS, S3 or other storage engines

yes (replicated cache)

yes

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

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

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

Security Hooks for custom implementations

yes

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.