DBMS > Memcached vs. RocksDB vs. STSdb vs. Vitess

System Properties Comparison Memcached vs. RocksDB vs. STSdb vs. Vitess

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

In-memory key-value store, originally intended for caching

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

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Key-value store

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	18.08
Rank	#32	Overall
	#4	Key-value stores

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

Score	0.10
Rank	#357	Overall
	#51	Key-value stores

Score	0.88
Rank	#203	Overall
	#95	Relational DBMS

Website

www.memcached.org

rocksdb.org

github.com/STSSoft/STSdb4

vitess.io

Technical documentation

github.com/memcached/memcached/wiki

github.com/facebook/rocksdb/wiki

vitess.io/docs

Developer

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

Facebook, Inc.

STS Soft SC

The Linux Foundation, PlanetScale

Initial release

2003

2013

2011

2013

Current release

1.6.27, May 2024

9.2.1, May 2024

4.0.8, September 2015

15.0.2, December 2022

License

Commercial or Open Source

Open Source

BSD license

Open Source

BSD

Open Source

GPLv2, commercial license 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.

Implementation language

C++

Server operating systems

FreeBSD
Linux
OS X
Unix
Windows

Linux

Windows

Docker
Linux
macOS

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

primitive types and user defined types (classes)

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

SQL

Support of SQL

yes

with proprietary extensions

APIs and other access methods

Proprietary protocol

C++ API
Java API

.NET Client API

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

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

C
C++
Go
Java
Perl
Python
Ruby

C#
Java

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

horizontal partitioning

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

Repcached, a Memcached patch, provides this functionallity

yes

none

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

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 at shard level

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

yes

using SASL (Simple Authentication and Security Layer) protocol

Users with fine-grained authorization concept

no user groups or 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.