DBMS > Elasticsearch vs. Graphite vs. Hazelcast vs. RocksDB vs. SpaceTime

System Properties Comparison Elasticsearch vs. Graphite vs. Hazelcast vs. RocksDB vs. SpaceTime

Editorial information provided by DB-Engines

Name

Description

A distributed, RESTful modern search and analytics engine based on Apache Lucene

Elasticsearch lets you perform and combine many types of searches such as structured, unstructured, geo, and metric

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)

SpaceTime is a spatio-temporal DBMS with a focus on performance.

Primary database model

Secondary database models

Document store
Spatial DBMS
Vector DBMS

Document store

JSON support with IMDG 3.12

Relational DBMS

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

Score	135.35
Rank	#7	Overall
	#1	Search engines

Score	4.57
Rank	#73	Overall
	#5	Time Series DBMS

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

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

Score	0.00
Rank	#383	Overall
	#7	Spatial DBMS

Website

www.elastic.co/elasticsearch

github.com/graphite-project/graphite-web

hazelcast.com

rocksdb.org

www.mireo.com/spacetime

Technical documentation

www.elastic.co/guide/en/elasticsearch/reference/current/index.html

graphite.readthedocs.io

hazelcast.org/imdg/docs

github.com/facebook/rocksdb/wiki

Developer

Elastic

Chris Davis

Hazelcast

Facebook, Inc.

Mireo

Initial release

2010

2006

2008

2013

2020

Current release

8.6, January 2023

5.3.6, November 2023

8.11.4, April 2024

License

Commercial or Open Source

Open Source

Elastic License

Open Source

Apache 2.0

Open Source

Apache Version 2; commercial licenses available

Open Source

BSD

commercial

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

All OS with a Java VM

Linux
Unix

All OS with a Java VM

Linux

Data scheme

schema-free

Flexible type definitions. Once a type is defined, it is persistent

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

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

All search fields are automatically indexed

yes

SQL

Support of SQL

SQL-like query language

A subset of ANSI SQL is implemented

APIs and other access methods

Java API
RESTful HTTP/JSON API

HTTP API
Sockets

JCache
JPA
Memcached protocol
RESTful HTTP API

C++ API
Java API

RESTful HTTP API

Supported programming languages

.Net
Groovy
Community Contributed Clients
Java
JavaScript
Perl
PHP
Python
Ruby

JavaScript (Node.js)
Python

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

C
C++
Go
Java
Perl
Python
Ruby

C#
C++
Python

Server-side scripts

Stored procedures

yes

Event Listeners, Executor Services

Triggers

yes

by using the 'percolation' feature

yes

Events

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

horizontal partitioning

Fixed-grid hypercubes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

yes

Replicated Map

yes

Real-time block device replication (DRBD)

MapReduce

Offers an API for user-defined Map/Reduce methods

ES-Hadoop Connector

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Synchronous doc based replication. Get by ID may show delays up to 1 sec. Configurable write consistency: one, quorum, all

none

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

Immediate Consistency

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

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.

Memcached and Redis integration

yes

User concepts

Access control

Role-based access control

yes

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.