DBMS > Cachelot.io vs. Heroic vs. Ignite vs. Percona Server for MongoDB vs. RocksDB

System Properties Comparison Cachelot.io vs. Heroic vs. Ignite vs. Percona Server for MongoDB vs. RocksDB

Editorial information provided by DB-Engines

Name

Description

In-memory caching system

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

Apache Ignite is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads, delivering in-memory speeds at petabyte scale.

A drop-in replacement for MongoDB Community Edition with enterprise-grade features.

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

Primary database model

Key-value store

Time Series DBMS

Key-value store
Relational DBMS

Document store

Key-value store

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

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	3.16
Rank	#96	Overall
	#15	Key-value stores
	#49	Relational DBMS

Score	0.52
Rank	#254	Overall
	#39	Document stores

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

Website

cachelot.io

github.com/spotify/heroic

ignite.apache.org

www.percona.com/mongodb/software/percona-server-for-mongodb

rocksdb.org

Technical documentation

spotify.github.io/heroic

apacheignite.readme.io/docs

docs.percona.com/percona-distribution-for-mongodb

github.com/facebook/rocksdb/wiki

Developer

Spotify

Apache Software Foundation

Percona

Facebook, Inc.

Initial release

2015

2014

2015

2013

Current release

Apache Ignite 2.6

3.4.10-2.10, November 2017

8.11.4, April 2024

License

Commercial or Open Source

Open Source

Simplified BSD License

Open Source

Apache 2.0

Open Source

Apache 2.0

Open Source

GPL Version 2

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

C++

Java

C++, Java, .Net

C++

Server operating systems

FreeBSD
Linux
OS X

Linux
OS X
Solaris
Windows

Linux

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

Secondary indexes

yes

via Elasticsearch

yes

SQL

Support of SQL

ANSI-99 for query and DML statements, subset of DDL

APIs and other access methods

Memcached protocol

HQL (Heroic Query Language, a JSON-based language)
HTTP API

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

proprietary protocol using JSON

C++ API
Java API

Supported programming languages

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
OCaml
Perl
PHP
Python
Ruby

C#
C++
Java
PHP
Python
Ruby
Scala

Actionscript
C
C#
C++
Clojure
ColdFusion
D
Dart
Delphi
Erlang
Go
Groovy
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Scala
Smalltalk

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes (compute grid and cache interceptors can be used instead)

JavaScript

Triggers

yes (cache interceptors and events)

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

yes (replicated cache)

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency
Immediate Consistency

Immediate Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

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

via In-Memory Engine

yes

User concepts

Access control

Security Hooks for custom implementations

Access rights for users and roles

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.