DBMS > KeyDB vs. Memcached vs. OpenTSDB vs. Snowflake vs. Tigris

System Properties Comparison KeyDB vs. Memcached vs. OpenTSDB vs. Snowflake vs. Tigris

Editorial information provided by DB-Engines

Name

Description

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

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

Scalable Time Series DBMS based on HBase

Cloud-based data warehousing service for structured and semi-structured data

A horizontally scalable, ACID transactional, document database available both as a fully managed cloud service and for deployment on self-managed infrastructure

Primary database model

Key-value store

Time Series DBMS

Relational DBMS

Document store
Key-value store
Search engine
Time Series DBMS

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

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

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

Score	1.68
Rank	#142	Overall
	#12	Time Series DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	0.09
Rank	#363	Overall
	#49	Document stores
	#54	Key-value stores
	#22	Search engines
	#38	Time Series DBMS

Website

github.com/Snapchat/KeyDB
keydb.dev

Technical documentation

docs.keydb.dev

github.com/memcached/memcached/wiki

opentsdb.net/docs/build/html/index.html

docs.snowflake.net/manuals/index.html

www.tigrisdata.com/docs

Developer

EQ Alpha Technology Ltd.

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

currently maintained by Yahoo and other contributors

Snowflake Computing Inc.

Tigris Data, Inc.

Initial release

2019

2003

2011

2014

2022

Current release

1.6.27, May 2024

License

Commercial or Open Source

Open Source

BSD-3

Open Source

BSD license

Open Source

LGPL

commercial

Open Source

Apache Version 2.0

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C++

Java

Server operating systems

Linux

FreeBSD
Linux
OS X
Unix
Windows

Linux
Windows

hosted

Linux
macOS
Windows

Data scheme

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

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

numeric data for metrics, strings for tags

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

by using the Redis Search module

yes

SQL

Support of SQL

yes

APIs and other access methods

Proprietary protocol

RESP - REdis Serialization Protoco

Proprietary protocol

HTTP API
Telnet API

CLI Client
JDBC
ODBC

CLI Client
gRPC
RESTful HTTP API

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

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

Erlang
Go
Java
Python
R
Ruby

JavaScript (Node.js)
Python

Go
Java
JavaScript (Node.js)

Server-side scripts

Stored procedures

Lua

user defined functions

Triggers

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

based on HBase

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

none

Repcached, a Memcached patch, provides this functionallity

selectable replication factor

based on HBase

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Strong eventual consistency with CRDTs

Immediate Consistency

based on HBase

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Optimistic locking, atomic execution of commands blocks and scripts

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

yes

yes, using FoundationDB

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

yes

using SASL (Simple Authentication and Security Layer) protocol

Users with fine-grained authorization concept, user roles and pluggable authentication

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.