DBMS > Apache Impala vs. RavenDB vs. SAP HANA vs. Splunk vs. Transbase

System Properties Comparison Apache Impala vs. RavenDB vs. SAP HANA vs. Splunk vs. Transbase

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for Hadoop

Open Source Operational and Transactional Enterprise NoSQL Document Database

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

Analytics Platform for Big Data

A resource-optimized, high-performance, universally applicable RDBMS

Primary database model

Secondary database models

Document store

Graph DBMS
Spatial DBMS
Time Series DBMS

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	12.45
Rank	#40	Overall
	#24	Relational DBMS

Score	2.84
Rank	#101	Overall
	#18	Document stores

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Score	89.10
Rank	#14	Overall
	#2	Search engines

Score	0.17
Rank	#334	Overall
	#148	Relational DBMS

Website

impala.apache.org

ravendb.net

www.sap.com/products/hana.html

www.splunk.com

www.transaction.de/en/products/transbase.html

Technical documentation

impala.apache.org/impala-docs.html

ravendb.net/docs

help.sap.com/hana

docs.splunk.com/Documentation/Splunk

www.transaction.de/en/products/transbase/features.html

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Hibernating Rhinos

SAP

Splunk Inc.

Transaction Software GmbH

Initial release

2013

2010

2003

1987

Current release

4.1.0, June 2022

5.4, July 2022

2.0 SPS07 (April 4, 2023), April 2023

Transbase 8.3, 2022

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

AGPL version 3, commercial license available

commercial

Limited free edition and free developer edition available

commercial

free development license

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

C++

C and C++

Server operating systems

Linux

Linux
macOS
Raspberry Pi
Windows

Appliance or cloud-service

Linux
OS X
Solaris
Windows

FreeBSD
Linux
macOS
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

yes

SQL

Support of SQL

SQL-like DML and DDL statements

SQL-like query language (RQL)

yes

Splunk Search Processing Language for search commands

yes

APIs and other access methods

JDBC
ODBC

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

JDBC
ODBC

HTTP REST

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

All languages supporting JDBC/ODBC

.Net
C#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

C#
Java
JavaScript
PHP
Python
Ruby

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

yes

SQLScript, R

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication

yes

Multi-source replication

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID, Cluster-wide transaction available

ACID

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

yes

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

Access rights for users, groups and roles

based on Apache Sentry and Kerberos

Authorization levels configured per client per database

yes

Access rights for users and roles

fine grained access rights according to SQL-standard

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.