DBMS > Cachelot.io vs. RocksDB

System Properties Comparison Cachelot.io vs. RocksDB

Please select another system to include it in the comparison.

Our visitors often compare Cachelot.io and RocksDB with Microsoft SQL Server.

Editorial information provided by DB-Engines

Name

Description

In-memory caching system

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

Primary database model

Key-value store

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

Score	0.06
Rank	#389	Overall
	#63	Key-value stores

Score	4.11
Rank	#90	Overall
	#13	Key-value stores

Website

cachelot.io

rocksdb.org

Technical documentation

github.com/facebook/rocksdb/wiki

Developer

Facebook, Inc.

Initial release

2015

2013

Current release

8.8.1, November 2023

License

Commercial or Open Source

Open Source

Simplified BSD License

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++

Server operating systems

FreeBSD
Linux
OS X

Linux

Data scheme

schema-free

Typing

predefined data types such as float or date

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

SQL

Support of SQL

APIs and other access methods

Memcached protocol

C++ API
Java API

Supported programming languages

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

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

Triggers

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Foreign keys

Referential integrity

Transaction concepts

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

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

User concepts

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.