DBMS > EsgynDB vs. HBase vs. Ignite vs. Splunk

System Properties Comparison EsgynDB vs. HBase vs. Ignite vs. Splunk

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

Wide-column store based on Apache Hadoop and on concepts of BigTable

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.

Analytics Platform for Big Data

Primary database model

Relational DBMS

Wide column store

Key-value store
Relational DBMS

Search engine

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

Score	0.23
Rank	#319	Overall
	#141	Relational DBMS

Score	31.25
Rank	#26	Overall
	#2	Wide column stores

Score	3.64
Rank	#89	Overall
	#13	Key-value stores
	#48	Relational DBMS

Score	88.71
Rank	#14	Overall
	#2	Search engines

Website

Technical documentation

hbase.apache.org/book.html

apacheignite.readme.io/docs

docs.splunk.com/Documentation/Splunk

Developer

Esgyn

Apache Software Foundation

Apache top-level project, originally developed by Powerset

Apache Software Foundation

Splunk Inc.

Initial release

2015

2008

2015

2003

Current release

2.3.4, January 2021

Apache Ignite 2.6

License

Commercial or Open Source

commercial

Open Source

Apache version 2

Open Source

Apache 2.0

commercial

Limited free edition and free developer edition available

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

C++, Java

Java

C++, Java, .Net

Server operating systems

Linux

Linux
Unix
Windows

using Cygwin

Linux
OS X
Solaris
Windows

Data scheme

yes

schema-free, schema definition possible

yes

Typing

predefined data types such as float or date

yes

options to bring your own types, AVRO

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

yes

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

Splunk Search Processing Language for search commands

APIs and other access methods

ADO.NET
JDBC
ODBC

Java API
RESTful HTTP API
Thrift

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

HTTP REST

Supported programming languages

All languages supporting JDBC/ODBC/ADO.Net

C
C#
C++
Groovy
Java
PHP
Python
Scala

C#
C++
Java
PHP
Python
Ruby
Scala

C#
Java
JavaScript
PHP
Python
Ruby

Server-side scripts

Stored procedures

Java Stored Procedures

yes

Coprocessors in Java

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

yes

Triggers

yes

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication between multi datacenters

Multi-source replication
Source-replica replication

yes (replicated cache)

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

yes (compute grid and hadoop accelerator)

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Single row ACID (across millions of columns)

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

fine grained access rights according to SQL-standard

Access Control Lists (ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC

Security Hooks for custom implementations

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

Cloudera's HBase PaaS offering now supports Complex Transactions
11 August 2021, Krishna Maheshwari (sponsor)

Why is Hadoop not listed in the DB-Engines Ranking?
13 May 2013, Paul Andlinger

show all

Enterprise Search Engines almost double their popularity in the last 12 months
2 July 2014, Paul Andlinger

show all

Recent citations in the news

Best Practices from Rackspace for Modernizing a Legacy HBase/Solr Architecture Using AWS Services | Amazon Web ...
9 October 2023, AWS Blog

Less Components, Higher Performance: Apache Doris instead of ClickHouse, MySQL, Presto, and HBase
20 October 2023, hackernoon.com

HBase: The database big data left behind
6 May 2016, InfoWorld

What Is HBase? (Definition, Uses, Benefits, Features)
22 December 2022, Built In

HBase Tutorial
24 February 2023, Simplilearn

provided by Google News

GridGain Announces Call for Speakers for Virtual Apache Ignite Summit 2024
8 February 2024, PR Newswire

GridGain Showcases Power of Apache Ignite at Community Over Code Conference
5 October 2023, Datanami

Apache Ignite: An Overview
6 September 2023, Open Source For You

ArcGIS and Apache Log4j Vulnerabilities
22 May 2023, Esri

What is Apache Ignite? How is Apache Ignite Used?
18 July 2022, The Stack

provided by Google News

Share this page