DBMS > KairosDB vs. Memcached vs. MySQL vs. Transbase

System Properties Comparison KairosDB vs. Memcached vs. MySQL vs. Transbase

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Distributed Time Series DBMS based on Cassandra or H2

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

Widely used open source RDBMS

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

Primary database model

Time Series DBMS

Key-value store

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	0.60
Rank	#238	Overall
	#20	Time Series DBMS

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

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	0.05
Rank	#355	Overall
	#150	Relational DBMS

Website

github.com/kairosdb/kairosdb

www.memcached.org

www.mysql.com

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

Technical documentation

kairosdb.github.io

github.com/memcached/memcached/wiki

dev.mysql.com/doc

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

Developer

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

Oracle

since 2010, originally MySQL AB, then Sun

Transaction Software GmbH

Initial release

2013

2003

1995

1987

Current release

1.2.2, November 2018

1.6.29, June 2024

9.0.0, July 2024

Transbase 8.3, 2022

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

BSD license

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

free development license

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

Java

C and C++

Server operating systems

Linux
OS X
Windows

FreeBSD
Linux
OS X
Unix
Windows

FreeBSD
Linux
OS X
Solaris
Windows

FreeBSD
Linux
macOS
Solaris
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

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

SQL

Support of SQL

yes

with proprietary extensions

yes

APIs and other access methods

Graphite protocol
HTTP REST
Telnet API

Proprietary protocol

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

Java
JavaScript

Node.js
PHP
Python

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

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Server-side scripts

Stored procedures

yes

proprietary syntax

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

based on Cassandra

none

Repcached, a Memcached patch, provides this functionallity

Multi-source replication
Source-replica 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

based on Cassandra
Immediate Consistency

based on Cassandra

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

ACID

not for MyISAM storage engine

yes

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

simple password-based access control

yes

using SASL (Simple Authentication and Security Layer) protocol

Users with fine-grained authorization concept

no user groups or roles

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.