DBMS > Drizzle vs. KeyDB vs. Transbase vs. VictoriaMetrics

System Properties Comparison Drizzle vs. KeyDB vs. Transbase vs. VictoriaMetrics

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

Description

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

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

A resource-optimized, high-performance, universally applicable RDBMS

A fast, cost-effective and scalable Time Series DBMS and monitoring solution

Primary database model

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

Score	0.71
Rank	#226	Overall
	#33	Key-value stores

Score	0.11
Rank	#341	Overall
	#150	Relational DBMS

Score	1.32
Rank	#162	Overall
	#14	Time Series DBMS

Website

github.com/Snapchat/KeyDB
keydb.dev

www.transaction.de/en/products/transbase.html

victoriametrics.com

Technical documentation

docs.keydb.dev

www.transaction.de/en/products/transbase/features.html

docs.victoriametrics.com
github.com/VictoriaMetrics/VictoriaMetrics/wiki

Developer

Drizzle project, originally started by Brian Aker

EQ Alpha Technology Ltd.

Transaction Software GmbH

VictoriaMetrics

Initial release

2008

2019

1987

2018

Current release

7.2.4, September 2012

Transbase 8.3, 2022

v1.91, May 2023

License

Commercial or Open Source

Open Source

GNU GPL

Open Source

BSD-3

commercial

free development license

Open Source

Apache Version 2.0

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

C and C++

Server operating systems

FreeBSD
Linux
OS X

Linux

FreeBSD
Linux
macOS
Solaris
Windows

FreeBSD
Linux
macOS
OpenBSD

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

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

yes

APIs and other access methods

JDBC

Proprietary protocol

RESP - REdis Serialization Protoco

ADO.NET
JDBC
ODBC
Proprietary native API

Graphite protocol
InfluxDB Line Protocol
OpenTSDB
Prometheus Query API
Prometheus Remote Read/Write

Supported programming languages

C
C++
Java
PHP

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#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Server-side scripts

Stored procedures

Lua

yes

Triggers

hooks for callbacks inside the server can be used.

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Source-replica replication

Synchronous replication

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

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Optimistic locking, atomic execution of commands blocks and scripts

yes

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

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

User concepts

Access control

Pluggable authentication mechanisms

e.g. LDAP, HTTP

simple password-based access control and ACL

fine grained access rights according to SQL-standard

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

MySQL won the April ranking; did its forks follow?
1 April 2015, Paul Andlinger

Has MySQL finally lost its mojo?
1 July 2013, Matthias Gelbmann

show all

Recent citations in the news

Oh, snap! Snap snaps up database developer KeyDB
12 May 2022, TechCrunch

Snap Acquires KeyDB for Open-Source Services
17 May 2022, XR Today

Garnet–open-source faster cache-store speeds up applications, services
18 March 2024, Microsoft

Dragonfly 1.0 Released For What Claims To Be The World's Fastest In-Memory Data Store
20 March 2023, Phoronix

Microsoft open-sources Garnet cache-store -- a Redis rival?
19 March 2024, The Stack

provided by Google News

Green coding - VictoriaMetrics: The efficiency vs complexity trade-off
15 May 2024, ComputerWeekly.com

KubeCon24: VictoriaMetrics' Simpler Alternative to Prometheus
20 March 2024, The New Stack

OpenTelemetry Is Too Complicated, VictoriaMetrics Says
1 April 2024, Datanami

How VictoriaMetrics' open source approach led to mass industry adoption
3 May 2024, Tech.eu

VictoriaMetrics Machine Learning takes monitoring to the next level
19 March 2024, businesswire.com

provided by Google News

Share this page