DBMS > Kdb vs. MySQL vs. ObjectBox vs. Transbase

System Properties Comparison Kdb vs. MySQL vs. ObjectBox vs. Transbase

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

High performance Time Series DBMS

Widely used open source RDBMS

Extremely fast embedded database for small devices, IoT and Mobile

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

Primary database model

Time Series DBMS
Vector DBMS

Relational DBMS

Key/Value like access via memcached API

Object oriented DBMS

Relational DBMS

Secondary database models

Relational DBMS

Document store
Spatial DBMS

Time Series DBMS

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

Score	7.70
Rank	#53	Overall
	#3	Time Series DBMS
	#1	Vector DBMS

Score	1087.72
Rank	#2	Overall
	#2	Relational DBMS

Score	1.22
Rank	#172	Overall
	#5	Object oriented DBMS

Score	0.15
Rank	#337	Overall
	#147	Relational DBMS

Website

kx.com

www.mysql.com

objectbox.io

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

Technical documentation

code.kx.com

dev.mysql.com/doc

docs.objectbox.io

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

Developer

Kx Systems, a division of First Derivatives plc

Oracle

since 2010, originally MySQL AB, then Sun

ObjectBox Limited

Transaction Software GmbH

Initial release

2000

kdb was released 2000, kdb+ in 2003

1995

2017

1987

Current release

3.6, May 2018

8.3.0, January 2024

Transbase 8.3, 2022

License

Commercial or Open Source

commercial

free 32-bit version

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

Apache License 2.0

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

C and C++

Server operating systems

Linux
OS X
Solaris
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Android
iOS
Linux
macOS
Windows

FreeBSD
Linux
macOS
Solaris
Windows

Data scheme

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

table attribute 'grouped'

yes

SQL

Support of SQL

SQL-like query language (q)

yes

with proprietary extensions

yes

APIs and other access methods

HTTP API
JDBC
Jupyter
Kafka
ODBC
WebSocket

ADO.NET
JDBC
ODBC
Proprietary native API

Proprietary native API

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

C
C#
C++
Go
J
Java
JavaScript
Lua
MatLab
Perl
PHP
Python
R
Scala

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

C
C++
Dart
Go
Java
JavaScript

planned (as of Jan 2019)
Kotlin
Python

planned (as of Jan 2019)
Swift

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

Server-side scripts

Stored procedures

user defined functions

yes

proprietary syntax

yes

Triggers

yes

with views

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication
Source-replica replication

online/offline synchronization between client and server

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

similar paradigm used for internal processing

Consistency concepts

Methods to ensure consistency in a distributed system

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

ACID

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

rights management via user accounts

Users with fine-grained authorization concept

no user groups or roles

yes

fine grained access rights according to SQL-standard

More information provided by the system vendor

Specific characteristics

Integrated columnar database & programming system for streaming, real time and historical...
» more

Competitive advantages

provides seamless scalability; runs on industry standard server platforms; is top-ranked...
» more

Typical application scenarios

tick database streaming sensor data massive intelligence applications oil and gas...
» more

Key customers

Goldman Sachs Morgan Stanley Merrill Lynch J.P. Morgan Deutsche Bank IEX Securities...
» more

Market metrics

kdb+ performance and reliability proven by our customers in critical infrastructure...
» more

Licensing and pricing models

upon request
» more

News

In-Memory Database Use Cases
15 February 2024

Data Viewer for Objects – announcing ObjectBox Admin
14 November 2023

Vector Databases for Edge AI
9 August 2023

Vector Database Release for Flutter / Dart + Python
13 June 2023

SQLite and SQLite alternatives – a comprehensive overview
7 June 2023

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.