DBMS > HEAVY.AI vs. InterSystems Caché vs. RocksDB vs. Splunk vs. Warp 10

System Properties Comparison HEAVY.AI vs. InterSystems Caché vs. RocksDB vs. Splunk vs. Warp 10

Editorial information provided by DB-Engines

Name

Caché is a deprecated database engine which is substituted with InterSystems IRIS. It therefore is removed from the DB-Engines Ranking.

Description

A high performance, column-oriented RDBMS, specifically developed to harness the massive parallelism of modern CPU and GPU hardware

A multi-model DBMS and application server

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

Analytics Platform for Big Data

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Primary database model

Relational DBMS

Key-value store
Object oriented DBMS
Relational DBMS

Key-value store

Search engine

Time Series DBMS

Secondary database models

Spatial DBMS

Document store

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

Score	1.64
Rank	#145	Overall
	#67	Relational DBMS

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

Score	89.10
Rank	#14	Overall
	#2	Search engines

Score	0.14
Rank	#344	Overall
	#32	Time Series DBMS

Website

github.com/heavyai/heavydb
www.heavy.ai

www.intersystems.com/products/cache

rocksdb.org

www.splunk.com

www.warp10.io

Technical documentation

docs.heavy.ai

docs.intersystems.com

github.com/facebook/rocksdb/wiki

docs.splunk.com/Documentation/Splunk

www.warp10.io/content/02_Getting_started

Developer

HEAVY.AI, Inc.

InterSystems

Facebook, Inc.

Splunk Inc.

SenX

Initial release

2016

1997

2013

2003

2015

Current release

5.10, January 2022

2018.1.4, May 2020

9.2.1, May 2024

License

Commercial or Open Source

Open Source

Apache Version 2; enterprise edition available

commercial

Open Source

BSD

commercial

Limited free edition and free developer edition available

Open Source

Apache License 2.0

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

C++

Java

Server operating systems

Linux

AIX
HP Open VMS
HP-UX
Linux
OS X
Solaris
Windows

Linux

Linux
OS X
Solaris
Windows

Linux
OS X
Windows

Data scheme

yes

depending on used data model

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

Secondary indexes

yes

SQL

Support of SQL

yes

Splunk Search Processing Language for search commands

APIs and other access methods

JDBC
ODBC
Thrift
Vega

.NET Client API
JDBC
ODBC
RESTful HTTP API

C++ API
Java API

HTTP REST

HTTP API
Jupyter
WebSocket

Supported programming languages

All languages supporting JDBC/ODBC/Thrift
Python

C#
C++
Java

C
C++
Go
Java
Perl
Python
Ruby

C#
Java
JavaScript
PHP
Python
Ruby

Server-side scripts

Stored procedures

yes

WarpScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Round robin

none

horizontal partitioning

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

Source-replica replication

yes

Multi-source replication

selectable replication factor

based on HBase

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

Immediate Consistency

based on HBase

Foreign keys

Referential integrity

yes

Transaction concepts

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

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

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 rights for users, groups and roles

Access rights for users and roles

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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.