DBMS > Hazelcast vs. Hyprcubd vs. Ingres vs. MySQL vs. TempoIQ

System Properties Comparison Hazelcast vs. Hyprcubd vs. Ingres vs. MySQL vs. TempoIQ

Editorial information provided by DB-Engines

Name

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

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

Description

A widely adopted in-memory data grid

Serverless Time Series DBMS

Well established RDBMS

Widely used open source RDBMS

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

Primary database model

Key-value store

Time Series DBMS

Relational DBMS

Key/Value like access via memcached API

Time Series DBMS

Secondary database models

Document store

JSON support with IMDG 3.12

Document store
Spatial DBMS

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	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Website

hazelcast.com

hyprcubd.com (offline)

www.actian.com/databases/ingres

www.mysql.com

tempoiq.com (offline)

Technical documentation

hazelcast.org/imdg/docs

docs.actian.com/ingres

dev.mysql.com/doc

Developer

Hazelcast

Hyprcubd, Inc.

Actian Corporation

Oracle

since 2010, originally MySQL AB, then Sun

TempoIQ

Initial release

2008

1974

originally developed at University Berkely in early 1970s

1995

2012

Current release

5.3.6, November 2023

11.2, May 2022

8.4.0, April 2024

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are 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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

Java

C and C++

Server operating systems

All OS with a Java VM

hosted

AIX
HP Open VMS
HP-UX
Linux
Solaris
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

schema-free

yes

schema-free

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

with proprietary extensions

APIs and other access methods

JCache
JPA
Memcached protocol
RESTful HTTP API

gRPC (https)

.NET Client API
JDBC
ODBC
proprietary protocol (OpenAPI)

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP API

Supported programming languages

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

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

C#
Java
JavaScript

Node.js
Python
Ruby

Server-side scripts

Stored procedures

yes

Event Listeners, Executor Services

yes

proprietary syntax

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 with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Replicated Map

Ingres Replicator

Multi-source replication
Source-replica 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

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

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

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

MVCC

yes

table locks or row locks depending on storage engine

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

no user groups or 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.