DBMS > Hazelcast vs. Hyprcubd vs. IBM Db2 Event Store vs. SQLite

System Properties Comparison Hazelcast vs. Hyprcubd vs. IBM Db2 Event Store vs. SQLite

Please select another system to include it in the comparison.

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

Distributed Event Store optimized for Internet of Things use cases

Widely used embeddable, in-process RDBMS

Primary database model

Key-value store

Time Series DBMS

Event Store
Time Series DBMS

Relational DBMS

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	0.27
Rank	#309	Overall
	#2	Event Stores
	#28	Time Series DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

hazelcast.com

hyprcubd.com (offline)

www.ibm.com/products/db2-event-store

www.sqlite.org

Technical documentation

hazelcast.org/imdg/docs

www.ibm.com/docs/en/db2-event-store

www.sqlite.org/docs.html

Developer

Hazelcast

Hyprcubd, Inc.

IBM

Dwayne Richard Hipp

Initial release

2008

2017

2000

Current release

5.3.6, November 2023

2.0

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available

commercial

free developer edition available

Open Source

Public Domain

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

Server operating systems

All OS with a Java VM

hosted

Linux

Linux, macOS, Windows for the developer addition

server-less

Data scheme

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

time, int, uint, float, string

yes

not rigid because of 'dynamic typing' concept.

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

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

yes

through the embedded Spark runtime

yes

SQL-92 is not fully supported

APIs and other access methods

JCache
JPA
Memcached protocol
RESTful HTTP API

gRPC (https)

ADO.NET
DB2 Connect
JDBC
ODBC
RESTful HTTP API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

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

C
C#
C++
Cobol
Delphi
Fortran
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby
Scala
Visual Basic

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

yes

Event Listeners, Executor Services

yes

Triggers

yes

Events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Replicated Map

Active-active shard replication

none

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

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

Concurrency

Support for concurrent manipulation of data

yes

No - written data is immutable

yes

via file-system locks

Durability

Support for making data persistent

yes

Yes - Synchronous writes to local disk combined with replication and asynchronous writes in parquet format to permanent shared storage

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

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.