DBMS > Hazelcast vs. Ingres vs. RocksDB vs. Splunk vs. TempoIQ

System Properties Comparison Hazelcast vs. Ingres vs. RocksDB vs. Splunk vs. TempoIQ

Editorial information provided by DB-Engines

Name

TempoIQ seems to be decommissioned. It will be removed from the DB-Engines ranking.

Description

A widely adopted in-memory data grid

Well established RDBMS

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Analytics Platform for Big Data

Scalable analytics DBMS for sensor data, provided as a service (SaaS)

Primary database model

Secondary database models

Document store

JSON support with IMDG 3.12

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

Score	5.46
Rank	#61	Overall
	#7	Key-value stores

Score	3.80
Rank	#82	Overall
	#44	Relational DBMS

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Score	89.10
Rank	#14	Overall
	#2	Search engines

Website

hazelcast.com

www.actian.com/databases/ingres

rocksdb.org

www.splunk.com

tempoiq.com (offline)

Technical documentation

hazelcast.org/imdg/docs

docs.actian.com/ingres

github.com/facebook/rocksdb/wiki

docs.splunk.com/Documentation/Splunk

Developer

Hazelcast

Actian Corporation

Facebook, Inc.

Splunk Inc.

TempoIQ

Initial release

2008

1974

originally developed at University Berkely in early 1970s

2013

2003

2012

Current release

5.3.6, November 2023

11.2, May 2022

9.2.1, May 2024

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available

commercial

Open Source

BSD

commercial

Limited free edition and free developer edition available

commercial

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Java

C++

Server operating systems

All OS with a Java VM

AIX
HP Open VMS
HP-UX
Linux
Solaris
Windows

Linux

Linux
OS X
Solaris
Windows

Data scheme

schema-free

yes

schema-free

yes

schema-free

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

the object must implement a serialization strategy

but tools for importing/exporting data from/to XML-files available

yes

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

yes

Splunk Search Processing Language for search commands

APIs and other access methods

JCache
JPA
Memcached protocol
RESTful HTTP API

.NET Client API
JDBC
ODBC
proprietary protocol (OpenAPI)

C++ API
Java API

HTTP REST

HTTP API

Supported programming languages

.Net
C#
C++
Clojure
Go
Java
JavaScript (Node.js)
Python
Scala

C
C++
Go
Java
Perl
Python
Ruby

C#
Java
JavaScript
PHP
Python
Ruby

C#
Java
JavaScript

Node.js
Python
Ruby

Server-side scripts

Stored procedures

yes

Event Listeners, Executor Services

yes

Triggers

yes

Events

yes

Realtime Alerts

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

Ingres Star to access multiple databases simultaneously

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Replicated Map

Ingres Replicator

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 or Eventual Consistency selectable by user

Raft Consensus Algorithm

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

one or two-phase-commit; repeatable reads; read commited

ACID

yes

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

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

Role-based access control

fine grained access rights according to SQL-standard

Access rights for users and roles

simple authentication-based access control

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.