DBMS > Hazelcast vs. Hyprcubd vs. Ingres vs. Snowflake vs. Splunk

System Properties Comparison Hazelcast vs. Hyprcubd vs. Ingres vs. Snowflake vs. Splunk

Editorial information provided by DB-Engines

Name

Hyprcubd seems to be discontinued. Therefore it is excluded from the DB-Engines ranking.

Description

A widely adopted in-memory data grid

Serverless Time Series DBMS

Well established RDBMS

Cloud-based data warehousing service for structured and semi-structured data

Analytics Platform for Big Data

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	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	89.10
Rank	#14	Overall
	#2	Search engines

Website

hazelcast.com

hyprcubd.com (offline)

www.actian.com/databases/ingres

www.snowflake.com

www.splunk.com

Technical documentation

hazelcast.org/imdg/docs

docs.actian.com/ingres

docs.snowflake.net/manuals/index.html

docs.splunk.com/Documentation/Splunk

Developer

Hazelcast

Hyprcubd, Inc.

Actian Corporation

Snowflake Computing Inc.

Splunk Inc.

Initial release

2008

1974

originally developed at University Berkely in early 1970s

2014

2003

Current release

5.3.6, November 2023

11.2, May 2022

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available

commercial

Limited free edition and free developer edition available

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

Server operating systems

All OS with a Java VM

hosted

AIX
HP Open VMS
HP-UX
Linux
Solaris
Windows

hosted

Linux
OS X
Solaris
Windows

Data scheme

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

yes

Typing

predefined data types such as float or date

yes

time, int, uint, float, string

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

gRPC (https)

.NET Client API
JDBC
ODBC
proprietary protocol (OpenAPI)

CLI Client
JDBC
ODBC

HTTP REST

Supported programming languages

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

JavaScript (Node.js)
Python

C#
Java
JavaScript
PHP
Python
Ruby

Server-side scripts

Stored procedures

yes

Event Listeners, Executor Services

yes

user defined functions

yes

Triggers

yes

Events

yes

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

Ingres Star to access multiple databases simultaneously

yes

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

Eventual Consistency

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

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

token access

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept, user roles and pluggable authentication

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.