DBMS > atoti vs. Graphite vs. Hazelcast vs. RocksDB

System Properties Comparison atoti vs. Graphite vs. Hazelcast vs. RocksDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

An in-memory DBMS combining transactional and analytical processing to handle the aggregation of ever-changing data.

Data logging and graphing tool for time series data

The storage layer (fixed size database) is called Whisper

A widely adopted in-memory data grid

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

Primary database model

Object oriented DBMS

Time Series DBMS

Key-value store

Secondary database models

Document store

JSON support with IMDG 3.12

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

Score	0.61
Rank	#243	Overall
	#10	Object oriented DBMS

Score	4.83
Rank	#67	Overall
	#4	Time Series DBMS

Score	5.46
Rank	#61	Overall
	#7	Key-value stores

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Website

atoti.io

github.com/graphite-project/graphite-web

hazelcast.com

rocksdb.org

Technical documentation

docs.atoti.io

graphite.readthedocs.io

hazelcast.org/imdg/docs

github.com/facebook/rocksdb/wiki

Developer

ActiveViam

Chris Davis

Hazelcast

Facebook, Inc.

Initial release

2006

2008

2013

Current release

5.3.6, November 2023

9.2.1, May 2024

License

Commercial or Open Source

commercial

free versions available

Open Source

Apache 2.0

Open Source

Apache Version 2; commercial licenses available

Open Source

BSD

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

Python

Java

C++

Server operating systems

Linux
Unix

All OS with a Java VM

Linux

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

Numeric data only

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

SQL

Support of SQL

Multidimensional Expressions (MDX)

SQL-like query language

APIs and other access methods

HTTP API
Sockets

JCache
JPA
Memcached protocol
RESTful HTTP API

C++ API
Java API

Supported programming languages

JavaScript (Node.js)
Python

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

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

Python

yes

Event Listeners, Executor Services

Triggers

yes

Events

Partitioning methods

Methods for storing different data on different nodes

Sharding, horizontal partitioning

none

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Replicated Map

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

Foreign keys

Referential integrity

Transaction concepts

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

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

yes

Concurrency

Support for concurrent manipulation of data

yes, multi-version concurrency control (MVCC)

yes

locking

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

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.