DBMS > Hazelcast vs. Hypertable vs. Linter vs. RocksDB vs. SiteWhere

System Properties Comparison Hazelcast vs. Hypertable vs. Linter vs. RocksDB vs. SiteWhere

Editorial information provided by DB-Engines

Name

Hypertable has stopped its further development with March 2016 and is removed from the DB-Engines ranking.

Description

A widely adopted in-memory data grid

An open source BigTable implementation based on distributed file systems such as Hadoop

RDBMS for high security requirements

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

M2M integration platform for persisting/querying time series data

Primary database model

Secondary database models

Document store

JSON support with IMDG 3.12

Spatial DBMS

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

Score	5.97
Rank	#57	Overall
	#6	Key-value stores

Score	0.09
Rank	#346	Overall
	#152	Relational DBMS

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Score	0.06
Rank	#356	Overall
	#35	Time Series DBMS

Website

hazelcast.com

linter.ru

rocksdb.org

github.com/sitewhere/sitewhere

Technical documentation

hazelcast.org/imdg/docs

github.com/facebook/rocksdb/wiki

sitewhere1.sitewhere.io/index.html

Developer

Hazelcast

Hypertable Inc.

relex.ru

Facebook, Inc.

SiteWhere

Initial release

2008

2009

1990

2013

2010

Current release

5.3.6, November 2023

0.9.8.11, March 2016

9.2.1, May 2024

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available

Open Source

GNU version 3. Commercial license available

commercial

Open Source

BSD

Open Source

Common Public Attribution License Version 1.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

Java

C++

C and C++

C++

Java

Server operating systems

All OS with a Java VM

Linux
OS X
Windows

an inofficial Windows port is available

AIX
Android
BSD
HP Open VMS
iOS
Linux
OS X
VxWorks
Windows

Linux

Linux
OS X
Windows

Data scheme

schema-free

yes

schema-free

predefined scheme

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

Secondary indexes

yes

restricted

only exact value or prefix value scans

yes

SQL

Support of SQL

SQL-like query language

yes

APIs and other access methods

JCache
JPA
Memcached protocol
RESTful HTTP API

C++ API
Thrift

ADO.NET
JDBC
LINQ
ODBC
OLE DB
Oracle Call Interface (OCI)

C++ API
Java API

HTTP REST

Supported programming languages

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

C++
Java
Perl
PHP
Python
Ruby

C
C#
C++
Java
Perl
PHP
Python
Qt
Ruby
Tcl

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

Event Listeners, Executor Services

yes

proprietary syntax with the possibility to convert from PL/SQL

Triggers

yes

Events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

horizontal partitioning

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Replicated Map

selectable replication factor on file system level

Source-replica replication

yes

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

Raft Consensus Algorithm

Immediate 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

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

Role-based access control

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

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.