DBMS > MySQL vs. OpenTSDB vs. Oracle Berkeley DB vs. Tkrzw

System Properties Comparison MySQL vs. OpenTSDB vs. Oracle Berkeley DB vs. Tkrzw

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Widely used open source RDBMS

Scalable Time Series DBMS based on HBase

Widely used in-process key-value store

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

Primary database model

Relational DBMS

Key/Value like access via memcached API

Time Series DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Key-value store

Secondary database models

Document store
Spatial DBMS

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

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	1.59
Rank	#140	Overall
	#12	Time Series DBMS

Score	1.88
Rank	#130	Overall
	#23	Key-value stores
	#3	Native XML DBMS

Score	0.00
Rank	#385	Overall
	#61	Key-value stores

Website

www.mysql.com

opentsdb.net

www.oracle.com/database/technologies/related/berkeleydb.html

dbmx.net/tkrzw

Technical documentation

dev.mysql.com/doc

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

docs.oracle.com/cd/E17076_05/html/index.html

Developer

Oracle

since 2010, originally MySQL AB, then Sun

currently maintained by Yahoo and other contributors

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Mikio Hirabayashi

Initial release

1995

2011

1994

2020

Current release

9.0.0, July 2024

18.1.40, May 2020

0.9.3, August 2020

License

Commercial or Open Source

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

LGPL

Open Source

commercial license available

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

Java

C, Java, C++ (depending on the Berkeley DB edition)

C++

Server operating systems

FreeBSD
Linux
OS X
Solaris
Windows

Linux
Windows

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Linux
macOS

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

numeric data for metrics, strings for tags

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

only with the Berkeley DB XML edition

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

SQL interfaced based on SQLite is available

APIs and other access methods

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP API
Telnet API

Supported programming languages

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

Erlang
Go
Java
Python
R
Ruby

.Net

Figaro is a .Net framework assembly that extends Berkeley DB XML into an embeddable database engine for .NET
others

Third-party libraries to manipulate Berkeley DB files are available for many languages
C
C#
C++
Java
JavaScript (Node.js)

3rd party binding
Perl
Python
Tcl

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

yes

proprietary syntax

Triggers

yes

only for the SQL API

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

based on HBase

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

selectable replication factor

based on HBase

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

based on HBase

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

not for MyISAM storage engine

ACID

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

using specific database classes

User concepts

Access control

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.