DBMS > Hazelcast vs. Machbase Neo vs. Riak TS vs. Yanza

System Properties Comparison Hazelcast vs. Machbase Neo vs. Riak TS vs. Yanza

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Yanza seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

A widely adopted in-memory data grid

TimeSeries DBMS for AIoT and BigData

Riak TS is a distributed NoSQL database optimized for time series data and based on Riak KV

Time Series DBMS for IoT Applications

Primary database model

Key-value store

Time Series 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.17
Rank	#337	Overall
	#30	Time Series DBMS

Score	0.28
Rank	#307	Overall
	#27	Time Series DBMS

Website

hazelcast.com

machbase.com

yanza.com

Technical documentation

hazelcast.org/imdg/docs

machbase.com/dbms

www.tiot.jp/riak-docs/riak/ts/latest

Developer

Hazelcast

Machbase

Open Source, formerly Basho Technologies

Yanza

Initial release

2008

2013

2015

Current release

5.3.6, November 2023

V8.0, August 2023

3.0.0, September 2022

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available

commercial

free test version available

Open Source

commercial

free version available

Cloud-based only

Only available as a cloud service

but mainly used as a service provided by Yanza

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

Erlang

Server operating systems

All OS with a Java VM

Linux
macOS
Windows

Linux
OS X

Windows

Data scheme

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

the object must implement a serialization strategy

Secondary indexes

yes

restricted

SQL

Support of SQL

SQL-like query language

yes, limited

APIs and other access methods

JCache
JPA
Memcached protocol
RESTful HTTP API

gRPC
HTTP REST
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC

HTTP API
Native Erlang Interface

HTTP API

Supported programming languages

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

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

any language that supports HTTP calls

Server-side scripts

Stored procedures

yes

Event Listeners, Executor Services

Erlang

Triggers

yes

Events

yes

pre-commit hooks and post-commit hooks

yes

Timer and event based

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

selectable replication factor

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

Immediate Consistency

Foreign keys

Referential integrity

links between datasets can be stored

Transaction concepts

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

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

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

volatile and lookup table

User concepts

Access control

Role-based access control

simple password-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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

Hazelcast appoints Anthony Griffin as Chief Architect -
11 June 2024, Enterprise Times

Hazelcast Weaves Wider Logic Threads Through The Data Fabric
7 March 2024, Forbes

Hazelcast 5.4 real time data processing platform boosts AI and consistency
17 April 2024, VentureBeat

Hazelcast Showcases Real-Time Data Platform at 2024 Gartner Summit
15 May 2024, Datanami

Real-Time Data Platform Hazelcast Introduces New Chief Technology Officer Adrian Soars
7 November 2023, Finovate

provided by Google News

Share this page