DBMS > BoltDB vs. KeyDB vs. RocksDB vs. Vitess

System Properties Comparison BoltDB vs. KeyDB vs. RocksDB vs. Vitess

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

An embedded key-value store for Go.

An ultra-fast, open source Key-value store fully compatible with Redis API, modules, and protocols

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

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	0.80
Rank	#215	Overall
	#31	Key-value stores

Score	0.70
Rank	#229	Overall
	#32	Key-value stores

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

Score	0.88
Rank	#203	Overall
	#95	Relational DBMS

Website

github.com/boltdb/bolt

github.com/Snapchat/KeyDB
keydb.dev

rocksdb.org

vitess.io

Technical documentation

docs.keydb.dev

github.com/facebook/rocksdb/wiki

vitess.io/docs

Developer

EQ Alpha Technology Ltd.

Facebook, Inc.

The Linux Foundation, PlanetScale

Initial release

2013

2019

2013

Current release

9.2.1, May 2024

15.0.2, December 2022

License

Commercial or Open Source

Open Source

MIT License

Open Source

BSD-3

Open Source

BSD

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

BSD
Linux
OS X
Solaris
Windows

Linux

Docker
Linux
macOS

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

partial

Supported data types are strings, hashes, lists, sets and sorted sets, bit arrays, hyperloglogs and geospatial indexes

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

by using the Redis Search module

yes

SQL

Support of SQL

yes

with proprietary extensions

APIs and other access methods

Proprietary protocol

RESP - REdis Serialization Protoco

C++ API
Java API

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

C
C#
C++
Clojure
Crystal
D
Dart
Elixir
Erlang
Fancy
Go
Haskell
Haxe
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Objective-C
OCaml
Pascal
Perl
PHP
Prolog
Pure Data
Python
R
Rebol
Ruby
Rust
Scala
Scheme
Smalltalk
Swift
Tcl
Visual Basic

C
C++
Go
Java
Perl
Python
Ruby

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

Lua

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication
Source-replica replication

yes

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

none

Eventual Consistency
Strong eventual consistency with CRDTs

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

Optimistic locking, atomic execution of commands blocks and scripts

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

Configurable mechanisms for persistency via snapshots and/or operations logs

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

simple password-based access control and ACL

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.