DBMS > Drizzle vs. GeoSpock vs. H2 vs. SAP HANA vs. Splunk

System Properties Comparison Drizzle vs. GeoSpock vs. H2 vs. SAP HANA vs. Splunk

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

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

Description

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

Spatial and temporal data processing engine for extreme data scale

Full-featured RDBMS with a small footprint, either embedded into a Java application or used as a database server.

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

Analytics Platform for Big Data

Primary database model

Relational DBMS

Search engine

Secondary database models

Time Series DBMS

Spatial 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	8.13
Rank	#49	Overall
	#31	Relational DBMS

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Score	86.45
Rank	#14	Overall
	#2	Search engines

Website

geospock.com

www.h2database.com

www.sap.com/products/hana.html

www.splunk.com

Technical documentation

www.h2database.com/html/main.html

help.sap.com/hana

docs.splunk.com/Documentation/Splunk

Developer

Drizzle project, originally started by Brian Aker

GeoSpock

Thomas Mueller

SAP

Splunk Inc.

Initial release

2008

2005

2010

2003

Current release

7.2.4, September 2012

2.0, September 2019

2.2.220, July 2023

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

GNU GPL

commercial

Open Source

dual-licence (Mozilla public license, Eclipse public license)

commercial

Limited free edition and free developer edition available

Cloud-based only

Only available as a cloud service

yes

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++

Java, Javascript

Java

Server operating systems

FreeBSD
Linux
OS X

hosted

All OS with a Java VM

Appliance or cloud-service

Linux
OS X
Solaris
Windows

Data scheme

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

yes

with proprietary extensions

ANSI SQL for query only (using Presto)

yes

Splunk Search Processing Language for search commands

APIs and other access methods

JDBC

JDBC
ODBC

HTTP REST

Supported programming languages

C
C++
Java
PHP

Java

C#
Java
JavaScript
PHP
Python
Ruby

Server-side scripts

Stored procedures

Java Stored Procedures and User-Defined Functions

SQLScript, R

yes

Triggers

hooks for callbacks inside the server can be used.

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Automatic sharding

none

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

With clustering: 2 database servers on different computers operate on identical copies of a database

yes

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

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

yes, multi-version concurrency control (MVCC)

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

Pluggable authentication mechanisms

e.g. LDAP, HTTP

Access rights for users can be defined per table

fine grained access rights according to SQL-standard

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.