DBMS > Cachelot.io vs. Heroic vs. RocksDB vs. SingleStore vs. Vitess

System Properties Comparison Cachelot.io vs. Heroic vs. RocksDB vs. SingleStore vs. Vitess

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

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

MySQL wire-compliant distributed RDBMS that combines an in-memory row-oriented and a disc-based column-oriented storage with patented universal storage to handle transactional and analytical workloads in one single table type

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Secondary database models

Document store
Spatial DBMS
Time Series DBMS
Vector DBMS

Document store
Spatial DBMS

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

Score	0.00
Rank	#396	Overall
	#64	Key-value stores

Score	0.57
Rank	#250	Overall
	#21	Time Series DBMS

Score	4.00
Rank	#84	Overall
	#11	Key-value stores

Score	5.91
Rank	#61	Overall
	#34	Relational DBMS

Score	1.04
Rank	#191	Overall
	#89	Relational DBMS

Website

cachelot.io

github.com/spotify/heroic

rocksdb.org

www.singlestore.com

vitess.io

Technical documentation

spotify.github.io/heroic

github.com/facebook/rocksdb/wiki

docs.singlestore.com

vitess.io/docs

Developer

Spotify

Facebook, Inc.

SingleStore Inc.

The Linux Foundation, PlanetScale

Initial release

2015

2014

2013

Current release

8.11.4, April 2024

8.5, January 2024

15.0.2, December 2022

License

Commercial or Open Source

Open Source

Simplified BSD License

Open Source

Apache 2.0

Open Source

BSD

commercial

free developer edition available

Open Source

Apache Version 2.0, commercial licenses available

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.

SingleStoreDB Cloud: The world's fastest, modern cloud database for both operational (OLTP) and analytical (OLAP) workloads. Available instantly with multi-cloud and hybrid-cloud capabilities

Implementation language

C++

Java

C++

C++, Go

Server operating systems

FreeBSD
Linux
OS X

Linux

64 bit version required

Docker
Linux
macOS

Data scheme

schema-free

yes

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.

Secondary indexes

yes

via Elasticsearch

yes

SQL

Support of SQL

yes

but no triggers and foreign keys

yes

with proprietary extensions

APIs and other access methods

Memcached protocol

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

C++ API
Java API

Cluster Management API

as HTTP Rest and CLI
HTTP API
JDBC
MongoDB API
ODBC

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

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

C
C++
Go
Java
Perl
Python
Ruby

Bash
C
C#
Java
JavaScript (Node.js)
Python

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning

Sharding

hash partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Source-replica replication

stores two copies of each physical data partition on two separate nodes

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

can define user-defined aggregate functions for map-reduce-style calculations

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency
Immediate Consistency

Immediate Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

yes

ACID

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

yes

table locks or row locks depending on storage engine

Durability

Support for making data persistent

yes

All updates are persistent, including those to disk-based columnstores and memory-based row stores. Transaction commits are supported via write-ahead log.

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

Fine grained access control via users, groups and roles

Users with fine-grained authorization concept

no user groups or roles

More information provided by the system vendor

Specific characteristics

SingleStore offers a fully-managed , distributed, highly-scalable SQL database designed...
» more

Competitive advantages

SingleStore’s competitive advantages include: Easy and Simplified Architecture with...
» more

Typical application scenarios

Driving Fast Analytics: SingleStore delivers the fastest and most scalable reporting...
» more

Key customers

IEX Cloud : Improves Financial Data Distribution Speed 15x with Singlestore DB Comcast,...
» more

Market metrics

Customers in various industries worldwide including US and International Industry...
» more

Licensing and pricing models

F ree Tier and Enterprise Edition
» more

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.