DBMS > Kdb vs. Manticore Search vs. MySQL vs. VictoriaMetrics

System Properties Comparison Kdb vs. Manticore Search vs. MySQL vs. VictoriaMetrics

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

High performance Time Series DBMS

Multi-storage database for search, including full-text search.

Widely used open source RDBMS

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

Primary database model

Time Series DBMS
Vector DBMS

Search engine

Relational DBMS

Key/Value like access via memcached API

Time Series DBMS

Secondary database models

Relational DBMS

Time Series DBMS

using the Manticore Columnar Library

Document store
Spatial DBMS

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

Score	7.71
Rank	#49	Overall
	#2	Time Series DBMS
	#1	Vector DBMS

Score	0.29
Rank	#302	Overall
	#21	Search engines

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	1.23
Rank	#172	Overall
	#15	Time Series DBMS

Website

Technical documentation

code.kx.com

manual.manticoresearch.com

dev.mysql.com/doc

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

Developer

Kx Systems, a division of First Derivatives plc

Manticore Software

Oracle

since 2010, originally MySQL AB, then Sun

VictoriaMetrics

Initial release

2000

kdb was released 2000, kdb+ in 2003

2017

1995

2018

Current release

3.6, May 2018

6.0, February 2023

8.4.0, April 2024

v1.91, May 2023

License

Commercial or Open Source

commercial

free 32-bit version

Open Source

GPL version 2

Open Source

GPL version 2. Commercial licenses with extended functionallity are 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.

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

Implementation language

C++

C and C++

Server operating systems

Linux
OS X
Solaris
Windows

FreeBSD
Linux
macOS
Windows

FreeBSD
Linux
OS X
Solaris
Windows

FreeBSD
Linux
macOS
OpenBSD

Data scheme

yes

Fixed schema

yes

Typing

predefined data types such as float or date

yes

Int, Bigint, Float, Timestamp, Bit, Int array, Bigint array, JSON, Boolean

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

Can index from XML

yes

Secondary indexes

yes

table attribute 'grouped'

yes

full-text index on all search fields

yes

SQL

Support of SQL

SQL-like query language (q)

SQL-like query language

yes

with proprietary extensions

APIs and other access methods

HTTP API
JDBC
Jupyter
Kafka
ODBC
WebSocket

Binary API
RESTful HTTP/JSON API
RESTful HTTP/SQL API
SQL over MySQL

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#
C++
Go
J
Java
JavaScript
Lua
MatLab
Perl
PHP
Python
R
Scala

Elixir
Go
Java
JavaScript (Node.js)
Perl
PHP
Python

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

Server-side scripts

Stored procedures

user defined functions

yes

proprietary syntax

Triggers

yes

with views

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

Partitioning is done manually, search queries against distributed index is supported

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Synchronous replication based on Galera library

Multi-source replication
Source-replica replication

Synchronous 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

Eventual Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

yes

isolated transactions for atomic changes and binary logging for safe writes

ACID

not for MyISAM storage engine

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

The original contents of fields are not stored in the Manticore index.

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

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

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.